CVE-2024-6119

HIGHPre-NVD 7.58.5
EchelonGraph scoreHIGH confidence

Score elevated to 8.5 because EPSS predicts 67% probability of exploitation within the next 30 days (top 0.8% of all CVEs). CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5 retained for reference (NVD's own analysis pending). Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: cisa-adp, epss, ghsa
Elevated
7.5
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 67%
CISA-KEV: Not listedEPSS: 67%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.5
EG Score
8.5(high)
EG Risk
80(Track)
EG Risk 80/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity85% × 45%
Exploitation67% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
99.2%
KEV
Not listed

Published

September 3, 2024

Last Modified

July 14, 2026

Advisory Details (5)

Auto-updated Jul 14, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 06d1dc3fa96a (openssl/openssl)

Fix landed in openssl/openssl commit 06d1dc3fa96a — awaiting tagged release

https://github.com/openssl/openssl/commit/06d1dc3fa96a2ba5a3e22735a033012aadc9f0d6
github_commit

commit 621f3729831b (openssl/openssl)

Fix landed in openssl/openssl commit 621f3729831b — awaiting tagged release

https://github.com/openssl/openssl/commit/621f3729831b05ee828a3203eddb621d014ff2b2
github_commit

commit 05f360d9e849 (openssl/openssl)

Fix landed in openssl/openssl commit 05f360d9e849 — awaiting tagged release

https://github.com/openssl/openssl/commit/05f360d9e849a1b277db628f1f13083a7f8dd04f
github_commit

commit 7dfcee2cd2a6 (openssl/openssl)

Fix landed in openssl/openssl commit 7dfcee2cd2a6 — awaiting tagged release

https://github.com/openssl/openssl/commit/7dfcee2cd2a63b2c64b9b4b0850be64cb695b0a0

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuqemu-efi-riscv64 (2025.02-3ubuntu2.2) @ plucky2026-05-21ubuntu
ubuntuopenssl (3.0.13-0ubuntu3.4) @ noble2026-05-21ubuntu
redhatservice-interconnect/skupper-site-controller-rhel9:1.5.5-42024-12-16redhat
redhatrhcos-417.94.202412040832-02024-12-11redhat
redhatservice-interconnect/skupper-site-controller-rhel9:1.4.7-32024-11-21redhat
redhatedk2-0:20231122-6.el9_4.42024-11-06redhat
redhatrhcos-416.94.202410020522-02024-10-09redhat
redhatservice-interconnect/skupper-site-controller-rhel9:1.4.7-22024-09-26redhat
redhatopenssl-1:3.0.7-28.el9_42024-09-18redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 7× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 02:45 UTCEG score recompute 1.00
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-20 17:07 UTCEPSS rescore
  4. 2026-07-19 02:28 UTCEPSS rescore
  5. 2026-07-19 02:28 UTCEPSS rescore
  6. 2026-07-18 10:03 UTCEPSS rescore
  7. 2026-07-16 17:02 UTCEPSS rescore
  8. 2026-07-15 16:57 UTCEPSS rescore
  9. 2026-07-15 01:59 UTCEPSS rescore
  10. 2026-07-15 01:59 UTCEPSS rescore
  11. 2026-07-13 06:12 UTCEPSS rescore
  12. 2026-07-12 05:45 UTCEPSS rescore
  13. 2026-07-11 08:26 UTCEPSS rescore
  14. 2026-07-11 02:41 UTCOSV refresh
  15. 2026-07-09 19:09 UTCEPSS rescore
  16. 2026-07-09 19:09 UTCEPSS rescore
  17. 2026-07-06 16:26 UTCEPSS rescore
  18. 2026-07-06 16:26 UTCEPSS rescore
  19. 2026-07-05 02:29 UTCEPSS rescore
  20. 2026-07-01 15:06 UTCEPSS rescore
  21. 2026-06-30 23:21 UTCEPSS rescore
  22. 2026-06-30 23:21 UTCEPSS rescore
  23. 2026-06-29 14:05 UTCEPSS rescore
  24. 2026-06-28 04:55 UTCEPSS rescore
  25. 2026-06-28 04:55 UTCEPSS rescore
Show 73 more
  1. 2026-06-25 13:49 UTCEPSS rescore
  2. 2026-06-25 13:49 UTCEPSS rescore
  3. 2026-06-24 14:04 UTCEPSS rescore
  4. 2026-06-24 14:04 UTCEPSS rescore
  5. 2026-06-23 21:32 UTCEPSS rescore
  6. 2026-06-22 10:02 UTCOSV refresh
  7. 2026-06-19 19:25 UTCEPSS rescore
  8. 2026-06-19 19:25 UTCEPSS rescore
  9. 2026-06-18 17:52 UTCEPSS rescore
  10. 2026-06-18 17:52 UTCEPSS rescore
  11. 2026-06-17 17:52 UTCEPSS rescore
  12. 2026-06-16 17:52 UTCEPSS rescore
  13. 2026-06-15 17:48 UTCEPSS rescore
  14. 2026-06-14 23:17 UTCEPSS rescore
  15. 2026-06-13 22:59 UTCEPSS rescore
  16. 2026-06-13 22:59 UTCEPSS rescore
  17. 2026-06-12 23:11 UTCEPSS rescore
  18. 2026-06-12 23:11 UTCEPSS rescore
  19. 2026-06-11 13:59 UTCEPSS rescore
  20. 2026-06-11 13:59 UTCEPSS rescore
  21. 2026-06-10 22:18 UTCEPSS rescore
  22. 2026-06-10 22:18 UTCEPSS rescore
  23. 2026-06-10 13:21 UTCEPSS rescore
  24. 2026-06-08 14:16 UTCEPSS rescore
  25. 2026-06-08 14:16 UTCEPSS rescore
  26. 2026-06-07 15:24 UTCEPSS rescore
  27. 2026-06-07 15:24 UTCEPSS rescore
  28. 2026-06-06 13:46 UTCEPSS rescore
  29. 2026-06-06 13:46 UTCEPSS rescore
  30. 2026-06-05 22:46 UTCEPSS rescore
  31. 2026-06-05 22:46 UTCEPSS rescore
  32. 2026-06-04 13:11 UTCEPSS rescore
  33. 2026-06-04 13:11 UTCEPSS rescore
  34. 2026-06-04 12:39 UTCOSV refresh
  35. 2026-06-02 20:12 UTCEPSS rescore
  36. 2026-06-02 20:12 UTCEPSS rescore
  37. 2026-06-01 13:51 UTCEPSS rescore
  38. 2026-06-01 13:51 UTCEPSS rescore
  39. 2026-06-01 13:51 UTCEPSS rescore
  40. 2026-05-31 22:30 UTCEPSS rescore
  41. 2026-05-31 22:30 UTCEPSS rescore
  42. 2026-05-31 00:16 UTCEPSS rescore
  43. 2026-05-31 00:16 UTCEPSS rescore
  44. 2026-05-29 13:43 UTCEPSS rescore
  45. 2026-05-28 13:44 UTCEPSS rescore
  46. 2026-05-28 13:44 UTCEPSS rescore
  47. 2026-05-28 13:44 UTCEPSS rescore
  48. 2026-05-27 13:40 UTCEPSS rescore
  49. 2026-05-27 13:40 UTCEPSS rescore
  50. 2026-05-26 13:43 UTCEPSS rescore
  51. 2026-05-26 13:43 UTCEPSS rescore
  52. 2026-05-26 07:18 UTCEPSS rescore
  53. 2026-05-26 07:18 UTCEPSS rescore
  54. 2026-05-26 07:18 UTCEPSS rescore
  55. 2026-05-22 21:16 UTCEPSS rescore
  56. 2026-05-22 21:16 UTCEPSS rescore
  57. 2026-05-22 21:16 UTCEPSS rescore
  58. 2026-05-22 21:16 UTCEPSS rescore
  59. 2026-05-21 23:38 UTCEG score recompute
  60. 2026-05-21 23:38 UTCVendor advisory
  61. 2026-05-21 23:38 UTCGHSA enrichment
  62. 2026-05-21 22:42 UTCEPSS rescore
  63. 2026-05-20 22:37 UTCEPSS rescore
  64. 2026-05-20 22:37 UTCEPSS rescore
  65. 2026-05-20 22:37 UTCEPSS rescore
  66. 2026-05-20 22:37 UTCEPSS rescore
  67. 2026-05-20 22:37 UTCEPSS rescore
  68. 2026-05-20 11:21 UTCEPSS rescore
  69. 2026-05-20 11:21 UTCEPSS rescore
  70. 2026-05-20 11:21 UTCEPSS rescore
  71. 2026-05-20 11:21 UTCEPSS rescore
  72. 2026-05-18 21:30 UTCEPSS rescore
  73. 2026-05-18 21:30 UTCEPSS rescore

Frequently asked(5)

What is CVE-2024-6119?
CVE-2024-6119 is a high vulnerability published on September 3, 2024. 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…
When was CVE-2024-6119 disclosed?
CVE-2024-6119 was first published in the National Vulnerability Database on September 3, 2024, with the most recent update on July 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2024-6119 actively exploited?
CVE-2024-6119 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2024-6119?
CVE-2024-6119 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.5.
How do I remediate CVE-2024-6119?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2024-6119, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2024-6119

Explore →

Is Your Infrastructure Affected by CVE-2024-6119?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.