Skip to main content
No exploitation reportedFix available

CVE-2024-6119

No exploitation reported by the sources we read.

  • Published2024-09-03
  • Fixed in3.3.2 · 3.2.3 · 3.1.7 · 3.0.15
  • WeaknessCWE-843

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

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.

Timeline

dates in UTC
  1. 2024-09-0316:15CVE publishedNVD
  2. 2026-10-2319:23EPSS crossed 10 %FIRST EPSS

Observed activity

isMalicious corpus · updated 2026-10-23 21:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2024-6119?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2024-6119?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD · CISA-ADP
OpenSSL
BranchAffectedFixed in
3.3≥ 3.3.0, < 3.3.23.3.2
3.2≥ 3.2.0, < 3.2.33.2.3
3.1≥ 3.1.0, < 3.1.73.1.7
3.0≥ 3.0.0, < 3.0.153.0.15
Netapp 500f firmwareversion to verify
BranchAffectedFixed in
—all versionsno fix published
Netapp a250 firmwareversion to verify
BranchAffectedFixed in
—all versionsno fix published

16 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Packages

  • edk2-toolsAlmaLinux:9all versions · fixed in 20231122-6.el9_4.4and 3 other packages
  • opensslAlmaLinux:9all versions · fixed in 1:3.0.7-28.el9_4and 3 other packages

Full record on NVD

Fix

  1. Update OpenSSL to 3.3.2 · 3.2.3 · 3.1.7 · 3.0.15

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • CISA-ADPSSVC decisionnone2024-09-03
  • OpenCVESSVC decisionnone—
  • CISA-ADPCVSS 3.17.52024-09-03
  • NVDCVSS 3.17.5read 2026-10-23
  • CNAweakness (CWE)CWE-843read 2026-10-23
  • NVDweakness (CWE)CWE-843read 2026-10-23
  • FIRST EPSSEPSS score66.6 %read 2026-10-23
  • OSVaffected packages—

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Published
2024-09-03
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2024-6119?

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.

Is CVE-2024-6119 actively exploited?

Active exploitation of CVE-2024-6119 has not been confirmed. Its EPSS score was 66.6% on 2026-10-23, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2024-6119?

CVE-2024-6119 has a CVSS v3 base score of 7.5 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.

Running OpenSSL? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database