CVE-2014-0224
A public proof of concept exists; no exploitation attested.
- Published2014-06-05
- Fixed in1.0.1h · 1.0.0m · 0.9.8za
- WeaknessCWE-326
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « 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
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.
Timeline
dates in UTC- 2014-06-0521:55CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
- 2026-10-2319:23EPSS crossed 10 %FIRST EPSS
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2014-0224?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2014-0224?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.0 | ≥ 1.0.1, < 1.0.1h | 1.0.1h | NVD |
| 1.0 | ≥ 1.0.0, < 1.0.0m | 1.0.0m | NVD |
| 0.9 | < 0.9.8za | 0.9.8za | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 4.x | = 4 | no fix published | NVD |
| 5.x | = 5 | no fix published | NVD |
| 6.0 | = 6.0 | no fix published | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 19.x | = 19 | no fix published | NVD |
| 20.x | = 20 | no fix published | NVD |
13 more products in the sources.
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Fix
- Update OpenSSL to 1.0.1h · 1.0.0m · 0.9.8za
Advisories and patches
- www.openssl.orgVendor Advisory
- www.oracle.comPatch
- www.oracle.comPatch
- www.oracle.comPatch
- www.oracle.comPatch
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 5 repositories, unverifiedTripwire/OpenSSL-CCS-Inject-Testiph0n3/CVE-2014-0224droptables/ccs-evalssllabs/openssl-ccs-cve-2014-0224secretnonempty/CVE-2014-0224 PoC-in-GitHub
Sources
- NVDCVSS 3.17.4read 2026-10-23
- NVDCVSS 2.05.8read 2026-10-23
- NVDweakness (CWE)CWE-326read 2026-10-23
- FIRST EPSSEPSS score95.3 %read 2026-10-23
- PoC-in-GitHubproof of concept5read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
- Published
- 2014-06-05
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2014-0224?
Is CVE-2014-0224 actively exploited?
What is the CVSS score for CVE-2014-0224?
Hear about the next vulnerability in your software
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 ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.