CVE-2014-0195

MEDIUMCVSS v2 · 6.86.8—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 6.8 — v2 rates that MEDIUM (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:M/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 100.0% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
6.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 100%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 100%CVSS v2: 6.8Exploit: Metasploit · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

The dtls1_reassemble_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 does not properly validate fragment lengths in DTLS ClientHello messages, which allows remote attackers to execute arbitrary code or cause a denial of service (buffer overflow and application crash) via a long non-initial fragment.

CVSS v2.0 (legacy)
6.8MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
6.8(low)
EG Risk
75(Track)
EG Risk 75/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
Severity68% × 45%
Exploitation100% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
100%
EPSS %ILE
100%
KEV
Not listed

Published

June 5, 2014

Last Modified

May 6, 2026

References (252)

Vendor Advisories for CVE-2014-0195(3)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenssl (1.0.1f-1ubuntu2.2) @ trusty2026-07-23ubuntu
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.

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 (14 versions)0.9.8o-4squeeze15—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
openssl1.0.1e-2 ... 1.0.1e-2+deb7u9 (10 versions)1.0.1e-2+deb7u10—

Weakness Classification(2)

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

Additional Vendor Advisories

(1)

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

Publicly available exploits

(2 references)

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

  • GitHub PoCricedu/CVE-2014-0195
    First seen Jun 10, 2014

    OpenSSL heap overflow PoC (CVE-2014-0195)

    Open source ↗
  • Metasploitauxiliary/dos/ssl/dtls_fragment_overflow✓ verified
    First seen Jun 5, 2014

    OpenSSL DTLS Fragment Buffer Overflow DoS

    Open source ↗

Frequently asked(4)

What is CVE-2014-0195?
CVE-2014-0195 is a medium vulnerability published on June 5, 2014. The dtls1reassemblefragment 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 does not properly validate fragment lengths in DTLS ClientHello messages, which allows remote attackers to execute arbitrary code or cause a denial of service (buffer overflow…
When was CVE-2014-0195 disclosed?
CVE-2014-0195 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-0195 actively exploited?
CVE-2014-0195 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 100% probability of exploitation in the next 30 days, which ranks it in the top 0.0% of all scored CVEs.
How do I remediate CVE-2014-0195?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-0195, 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-0195

Explore →

Is Your Infrastructure Affected by CVE-2014-0195?

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

Start Free Scan →Browse All CVEs