CVE-2014-0224

CRITICALNVD 7.49.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 95% probability of exploitation within the next 30 days (top 0.1% of all CVEs). NVD baseline CVSS 7.4 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
9.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 95%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 95%CVSS: 7.4Exploit: Metasploit · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCipherSpec messages, which allows man-in-the-middle attackers to trigger use of a zero-length master key in certain OpenSSL-to-OpenSSL communications, and consequently hijack sessions or obtain sensitive information, via a crafted TLS handshake, aka the "CCS Injection" vulnerability.

CVSS v3
7.4
EG Score
9.0(high)
EG Risk
83(Track)
EG Risk 83/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
Severity90% × 45%
Exploitation95% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
95%
EPSS %ILE
100%
KEV
Not listed

Published

June 5, 2014

Last Modified

May 6, 2026

Advisory Details (4)

Auto-updated May 7, 2026
No patch confirmed yet.
generic

linux.oracle.com | ELSA-2014-1053

http://linux.oracle.com/errata/ELSA-2014-1053.html
generic

CEC Juniper Community

http://kb.juniper.net/InfoCenter/index?page=content&id=KB29217
generic

CEC Juniper Community

http://kb.juniper.net/InfoCenter/index?page=content&id=KB29195
generic

CEC Juniper Community

http://kb.juniper.net/InfoCenter/index?page=content&id=JSA10629

Vendor Advisories for CVE-2014-0224(4)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl (1.0.1f-1ubuntu2.2) @ trusty2026-05-28ubuntu
redhatopenssl098e-0:0.9.8e-29.el7_0.22014-06-10redhat
redhatopenssl-1:1.0.1e-34.el7_0.32014-06-10redhat
redhatopenssl-0:1.0.1e-16.el6_5.142014-06-05redhat
redhatopenssl-0:1.0.0-27.el6_4.42014-06-05redhat
redhatpatch2014-06-05redhat
redhatopenssl2014-06-05redhat
redhatrhev-hypervisor6-0:6.5-20140603.1.el6ev2014-06-05redhat
redhatopenssl-0:0.9.8e-27.el5_10.32014-06-05redhat
redhatopenssl098e-0:0.9.8e-18.el6_5.22014-06-05redhat
redhatpatch2014-06-05redhat
redhatpatch2014-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.

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.1h-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.1h-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.1h-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.1h-1—
Debian:6.0(1)
PackageVulnerable rangeFixed inDependents
openssl0.9.8o-4 ... 0.9.8o-4squeeze9 (15 versions)0.9.8o-4squeeze16—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
openssl1.0.1e-2 ... 1.0.1e-2+deb7u9 (10 versions)1.0.1e-2+deb7u10—

Weakness Classification(1)

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

Additional Vendor Advisories

(9)

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

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (3 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCsecretnonempty/CVE-2014-0224
    First seen Jul 16, 2014
    Open source ↗
  • GitHub PoCssllabs/openssl-ccs-cve-2014-0224
    First seen Jul 15, 2014
    Open source ↗
  • GitHub PoCTripwire/OpenSSL-CCS-Inject-Test
    First seen Jun 12, 2014

    This script is designed for detection of vulnerable servers (CVE-2014-0224.) in a wide range of configurations. It attempts to negotiate using each affected protocol version (SSLv3, TLSv1, TLSv1.1, and TLSv1.2) advertising a comprehensive set of ciphers.

    Open source ↗
  • Metasploitauxiliary/scanner/ssl/openssl_ccs✓ verified
    First seen Jun 5, 2014

    OpenSSL Server-Side ChangeCipherSpec Injection Scanner

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2014-0224?
CVE-2014-0224 is a critical vulnerability published on June 5, 2014. OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCipherSpec messages, which allows man-in-the-middle attackers to trigger use of a zero-length master key in certain OpenSSL-to-OpenSSL communications, and consequently hijack sessions…
When was CVE-2014-0224 disclosed?
CVE-2014-0224 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-0224 actively exploited?
CVE-2014-0224 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95% probability of exploitation in the next 30 days, which ranks it in the top 0.1% of all scored CVEs.
What is the CVSS score of CVE-2014-0224?
CVE-2014-0224 has a CVSS v3 base score of 7.4 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2014-0224?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-0224, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2014-0224

Explore →

Is Your Infrastructure Affected by CVE-2014-0224?

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

Start Free Scan →Browse All CVEs