CVE-2014-0221

NONECVSS 0.0Trending — 5 sources updated this weekElevated
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 88%
CISA-KEV: Not listedEPSS: 88%CVSS: Exploit: NoneExposed: 0

A fix is available — apply it.

The dtls1_get_message_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h allows remote attackers to cause a denial of service (recursion and client crash) via a DTLS hello message in an invalid DTLS handshake.

CVSS v3
EG Score
0.0(none)
EG Risk
0
EG Risk 0/100

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. It is distinct from the 0–10 EG Score, which measures severity.

EPSS
99.7%
KEV
Not listed

Published

June 5, 2014

Last Modified

May 6, 2026

Vendor Advisories for CVE-2014-0221(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl (1.0.1f-1ubuntu2.2) @ trusty2026-07-23ubuntu
redhatpatch2014-08-21redhat
redhatopenssl-0:0.9.8e-27.el5_10.42014-08-13redhat
redhatopenssl2014-08-06redhat
redhatopenssl-1:1.0.1e-34.el7_0.32014-06-10redhat
redhatopenssl-0:1.0.1e-16.el6_5.142014-06-05redhat

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.

Additional Vendor Advisories

(4)

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

Frequently asked(4)

What is CVE-2014-0221?
CVE-2014-0221 is a none vulnerability published on June 5, 2014. The dtls1getmessagefragment function in d1both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h allows remote attackers to cause a denial of service (recursion and client crash) via a DTLS hello message in an invalid DTLS handshake.
When was CVE-2014-0221 disclosed?
CVE-2014-0221 was first published in the National Vulnerability Database on June 5, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2014-0221 actively exploited?
CVE-2014-0221 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2014-0221?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-0221, 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-2014-0221

Explore →

Is Your Infrastructure Affected by CVE-2014-0221?

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