CVE-2024-6119
Last modified
CVE-2024-6119 is a high-severity vulnerability rated 7.5/10 on the CVSS scale. 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. EPSS estimates a 66.59% chance of exploitation in the next 30 days.
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
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Openssl | Openssl | >= 3.0.0, < 3.0.15 |
| Openssl | Openssl | >= 3.1.0, < 3.1.7 |
| Openssl | Openssl | >= 3.2.0, < 3.2.3 |
| Openssl | Openssl | >= 3.3.0, < 3.3.2 |
| Netapp | Active Iq Unified Manager | All versions |
| Netapp | Management Services For Element Software And Netapp Hci | All versions |
| Netapp | Ontap 9 | All versions |
| Netapp | Ontap Select Deploy Administration Utility | All versions |
| Netapp | Ontap Tools | 9 |
| Netapp | Brocade Fabric Operating System | All versions |
| Netapp | H300s Firmware | All versions |
| Netapp | H500s Firmware | All versions |
| Netapp | H700s Firmware | All versions |
| Netapp | H410s Firmware | All versions |
| Netapp | H410c Firmware | All versions |
| Netapp | H610c Firmware | All versions |
| Netapp | H610s Firmware | All versions |
| Netapp | H615c | All versions |
| Netapp | Bootstrap Os | All versions |
| Netapp | A250 Firmware | All versions |
| Netapp | 500f Firmware | All versions |
| Netapp | C250 Firmware | All versions |
References
- https://openssl-library.org/news/secadv/20240903.txtVendor Advisory
- https://security.netapp.com/advisory/ntap-20240912-0001/Third Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2024-6119?
How severe is CVE-2024-6119?
How do I fix CVE-2024-6119?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2024
- CVE-2024-6113A vulnerability was found in itsourcecode Monbela Tourist In…9.8
- CVE-2024-6114A vulnerability classified as critical has been found in its…9.8
- CVE-2024-6115A vulnerability classified as critical was found in itsource…9.8
- CVE-2024-6116A vulnerability, which was classified as critical, has been …9.8
- CVE-2024-6117A Unrestricted upload of file with dangerous type vulnerabil…8.8
- CVE-2024-6118A Plaintext Storage of a Password vulnerability in ebooknote…9.1
- CVE-2024-6120The Sparkle Demo Importer plugin for WordPress is vulnerable…6.5
- CVE-2024-6121An out-of-date version of Redis shipped with NI SystemLink S…7.8
- CVE-2024-6122An incorrect permission in the installation directory for th…5.5
- CVE-2024-6123The Bit Form plugin for WordPress is vulnerable to arbitrary…7.2
- CVE-2024-6124Reflected XSS in M-Files Hubshare before version 5.0.6.0 all…5.4
- CVE-2024-6125The Login with phone number plugin for WordPress is vulnerab…8.1
Are you affected by CVE-2024-6119?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
