You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
This CVE record has been updated after NVD enrichment efforts were completed. Enrichment data supplied by the NVD may require amendment due to these changes.
Description
Issue summary: Applications performing certificate name checks (e.g., TLS
clients checking server certificates) may attempt to read an invalid memory
address resulting in abnormal termination of the application process.
Impact summary: Abnormal termination of an application can a cause a denial of
service.
Applications performing certificate name checks (e.g., TLS clients checking
server certificates) may attempt to read an invalid memory address when
comparing the expected name with an `otherName` subject alternative name of an
X.509 certificate. This may result in an exception that terminates the
application program.
Note that basic certificate chain validation (signatures, dates, ...) is not
affected, the denial of service can occur only when the application also
specifies an expected DNS name, Email address or IP address.
TLS servers rarely solicit client certificates, and even when they do, they
generally don't perform a name check against a reference identifier (expected
identity), but rather extract the presented identity after checking the
certificate chain. So TLS servers are generally not affected and the severity
of the issue is Moderate.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
AND
OR
*cpe:2.3:h:netapp:h615c:-:*:*:*:*:*:*:*
OR
cpe:2.3:o:netapp:h615c_firmware:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:netapp:500f_firmware:-:*:*:*:*:*:*:*
OR
cpe:2.3:h:netapp:500f:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:netapp:a250_firmware:-:*:*:*:*:*:*:*
OR
cpe:2.3:h:netapp:a250:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:netapp:bootstrap_os:-:*:*:*:*:*:*:*
OR
cpe:2.3:h:netapp:hci_compute_node:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:netapp:c250_firmware:-:*:*:*:*:*:*:*
OR
cpe:2.3:h:netapp:c250:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:netapp:h300s_firmware:-:*:*:*:*:*:*:*
OR
cpe:2.3:h:netapp:h300s:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:netapp:h410c_firmware:-:*:*:*:*:*:*:*
OR
cpe:2.3:h:netapp:h410c:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:netapp:h410s_firmware:-:*:*:*:*:*:*:*
OR
cpe:2.3:h:netapp:h410s:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:netapp:h500s_firmware:-:*:*:*:*:*:*:*
OR
cpe:2.3:h:netapp:h500s:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:netapp:h610c_firmware:-:*:*:*:*:*:*:*
OR
cpe:2.3:h:netapp:h610c:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:netapp:h610s_firmware:-:*:*:*:*:*:*:*
OR
cpe:2.3:h:netapp:h610s:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:netapp:h700s_firmware:-:*:*:*:*:*:*:*
OR
cpe:2.3:h:netapp:h700s:-:*:*:*:*:*:*:*
Added
CPE Configuration
OR
*cpe:2.3:a:netapp:ontap_select_deploy_administration_utility:-:*:*:*:*:*:*:*
*cpe:2.3:a:netapp:active_iq_unified_manager:-:*:*:*:*:vmware_vsphere:*:*
*cpe:2.3:a:netapp:management_services_for_element_software_and_netapp_hci:-:*:*:*:*:*:*:*
*cpe:2.3:a:netapp:ontap_9:-:*:*:*:*:*:*:*
*cpe:2.3:o:netapp:brocade_fabric_operating_system:-:*:*:*:*:*:*:*
*cpe:2.3:a:netapp:ontap_tools:9:*:*:*:*:vmware_vsphere:*:*
Added
CPE Configuration
OR
*cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.0.0 up to (excluding) 3.0.15
*cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.1.0 up to (excluding) 3.1.7
*cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.2.0 up to (excluding) 3.2.3
*cpe:2.3:a:openssl:openssl:*:*:*:*:*:*:*:* versions from (including) 3.3.0 up to (excluding) 3.3.2
Added
Reference Type
CVE: http://www.openwall.com/lists/oss-security/2024/09/03/4 Types: Mailing List
Added
Reference Type
CVE: https://lists.freebsd.org/archives/freebsd-security/2024-September/000303.html Types: Mailing List
Added
Reference Type
CVE: https://security.netapp.com/advisory/ntap-20240912-0001/ Types: Third Party Advisory
New CVE Received from OpenSSL Software Foundation9/03/2024 12:15:07 PM
Action
Type
Old Value
New Value
Added
Description
Issue summary: Applications performing certificate name checks (e.g., TLS
clients checking server certificates) may attempt to read an invalid memory
address resulting in abnormal termination of the application process.
Impact summary: Abnormal termination of an application can a cause a denial of
service.
Applications performing certificate name checks (e.g., TLS clients checking
server certificates) may attempt to read an invalid memory address when
comparing the expected name with an `otherName` subject alternative name of an
X.509 certificate. This may result in an exception that terminates the
application program.
Note that basic certificate chain validation (signatures, dates, ...) is not
affected, the denial of service can occur only when the application also
specifies an expected DNS name, Email address or IP address.
TLS servers rarely solicit client certificates, and even when they do, they
generally don't perform a name check against a reference identifier (expected
identity), but rather extract the presented identity after checking the
certificate chain. So TLS servers are generally not affected and the severity
of the issue is Moderate.
The FIPS modules in 3.3, 3.2, 3.1 and 3.0 are not affected by this issue.
Added
CWE
OpenSSL Software Foundation CWE-843
Added
Reference
OpenSSL Software Foundation https://github.com/openssl/openssl/commit/05f360d9e849a1b277db628f1f13083a7f8dd04f [No types assigned]
Added
Reference
OpenSSL Software Foundation https://github.com/openssl/openssl/commit/06d1dc3fa96a2ba5a3e22735a033012aadc9f0d6 [No types assigned]
Added
Reference
OpenSSL Software Foundation https://github.com/openssl/openssl/commit/621f3729831b05ee828a3203eddb621d014ff2b2 [No types assigned]
Added
Reference
OpenSSL Software Foundation https://github.com/openssl/openssl/commit/7dfcee2cd2a63b2c64b9b4b0850be64cb695b0a0 [No types assigned]
Added
Reference
OpenSSL Software Foundation https://openssl-library.org/news/secadv/20240903.txt [No types assigned]
Quick Info
CVE Dictionary Entry: CVE-2024-6119 NVD
Published Date: 09/03/2024 NVD
Last Modified: 06/17/2026
Source: OpenSSL Software Foundation