CVE-2018-0732

HIGHNVD 7.58.0
EchelonGraph scoreHIGH confidence

Score elevated to 8.0 because EPSS predicts 49% probability of exploitation within the next 30 days (top 1.2% of all CVEs). NVD baseline CVSS 7.5 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Trending — 3 sources updated this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 49%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

During key agreement in a TLS handshake using a DH(E) based ciphersuite a malicious server can send a very large prime value to the client. This will cause the client to spend an unreasonably long period of time generating a key for this prime resulting in a hang until the client has finished. This could be exploited in a Denial Of Service attack. Fixed in OpenSSL 1.1.0i-dev (Affected 1.1.0-1.1.0h). Fixed in OpenSSL 1.0.2p-dev (Affected 1.0.2-1.0.2o).

CVSS v3
7.5
EG Score
8.0(high)
EG Risk
60(Track)
EG Risk 60/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
Severity80% × 45%
Exploitation49% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
98.8%
KEV
Not listed

Published

June 12, 2018

Last Modified

November 21, 2024

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulibssl1.0.0 (1.0.1-4ubuntu5.43) @ precise2026-05-28ubuntu
ubuntuopenssl1.0 (1.0.2n-1ubuntu5.1) @ bionic2026-05-28ubuntu
redhatopenssl2019-06-18redhat
redhatpatch2019-05-30redhat
redhatjbcs-httpd24-openssl-1:1.0.2n-15.jbcs.el72019-05-30redhat
redhatopenssl-1:1.0.2k-16.el72018-10-30redhat
redhatrhoar-nodejs-1:10.9.0-1.el72018-08-22redhat
redhatrhoar-nodejs-1:8.11.4-2.el72018-08-22redhat

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.

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 11× in last 7d / 31× 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 01:31 UTCEG score recompute 0.50
  2. 2026-07-22 22:11 UTCEG score recompute
  3. 2026-07-22 14:04 UTCEPSS rescore
  4. 2026-07-21 15:21 UTCEPSS rescore
  5. 2026-07-21 11:17 UTCOSV refresh
  6. 2026-07-20 17:04 UTCEPSS rescore
  7. 2026-07-20 17:04 UTCEPSS rescore
  8. 2026-07-19 02:26 UTCEPSS rescore
  9. 2026-07-19 02:26 UTCEPSS rescore
  10. 2026-07-16 16:59 UTCEPSS rescore
  11. 2026-07-16 16:59 UTCEPSS rescore
  12. 2026-07-15 16:55 UTCEPSS rescore
  13. 2026-07-15 16:54 UTCEPSS rescore
  14. 2026-07-13 22:26 UTCEPSS rescore
  15. 2026-07-13 22:26 UTCEPSS rescore
  16. 2026-07-11 08:24 UTCEPSS rescore
  17. 2026-07-09 19:06 UTCEPSS rescore
  18. 2026-07-07 13:42 UTCEPSS rescore
  19. 2026-07-05 02:27 UTCEPSS rescore
  20. 2026-07-04 06:56 UTCOSV refresh
  21. 2026-07-02 16:54 UTCEPSS rescore
  22. 2026-07-01 15:03 UTCEPSS rescore
  23. 2026-06-29 14:03 UTCEPSS rescore
  24. 2026-06-28 04:53 UTCEPSS rescore
  25. 2026-06-28 04:53 UTCEPSS rescore
Show 37 more
  1. 2026-06-27 03:06 UTCEPSS rescore
  2. 2026-06-25 13:47 UTCEPSS rescore
  3. 2026-06-24 14:02 UTCEPSS rescore
  4. 2026-06-24 14:02 UTCEPSS rescore
  5. 2026-06-23 21:30 UTCEPSS rescore
  6. 2026-06-23 21:30 UTCEPSS rescore
  7. 2026-06-22 14:23 UTCEPSS rescore
  8. 2026-06-22 14:23 UTCEPSS rescore
  9. 2026-06-21 01:57 UTCEPSS rescore
  10. 2026-06-21 01:57 UTCEPSS rescore
  11. 2026-06-19 19:23 UTCEPSS rescore
  12. 2026-06-19 19:23 UTCEPSS rescore
  13. 2026-06-18 17:50 UTCEPSS rescore
  14. 2026-06-17 17:50 UTCEPSS rescore
  15. 2026-06-16 17:50 UTCEPSS rescore
  16. 2026-06-15 18:13 UTCOSV refresh
  17. 2026-06-15 17:45 UTCEPSS rescore
  18. 2026-06-12 23:09 UTCEPSS rescore
  19. 2026-06-12 23:09 UTCEPSS rescore
  20. 2026-06-10 22:15 UTCEPSS rescore
  21. 2026-06-07 15:22 UTCEPSS rescore
  22. 2026-06-07 15:22 UTCEPSS rescore
  23. 2026-06-06 13:45 UTCEPSS rescore
  24. 2026-06-06 13:45 UTCEPSS rescore
  25. 2026-06-05 06:08 UTCEPSS rescore
  26. 2026-06-05 06:08 UTCEPSS rescore
  27. 2026-06-04 13:10 UTCEPSS rescore
  28. 2026-06-04 13:10 UTCEPSS rescore
  29. 2026-06-01 13:49 UTCEPSS rescore
  30. 2026-06-01 13:49 UTCEPSS rescore
  31. 2026-05-31 22:28 UTCEPSS rescore
  32. 2026-05-29 13:41 UTCEPSS rescore
  33. 2026-05-28 06:44 UTCEG score recompute
  34. 2026-05-28 06:44 UTCVendor advisory
  35. 2026-05-28 06:44 UTCGHSA enrichment
  36. 2026-05-26 13:42 UTCEPSS rescore
  37. 2026-05-23 18:05 UTCOSV refresh

Frequently asked(5)

What is CVE-2018-0732?
CVE-2018-0732 is a high vulnerability published on June 12, 2018. During key agreement in a TLS handshake using a DH(E) based ciphersuite a malicious server can send a very large prime value to the client. This will cause the client to spend an unreasonably long period of time generating a key for this prime resulting in a hang until the client has finished. This…
When was CVE-2018-0732 disclosed?
CVE-2018-0732 was first published in the National Vulnerability Database on June 12, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-0732 actively exploited?
CVE-2018-0732 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-0732?
CVE-2018-0732 has a CVSS v3 base score of 7.5 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.0.
How do I remediate CVE-2018-0732?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-0732, 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-2018-0732

Explore →

Is Your Infrastructure Affected by CVE-2018-0732?

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