CVE-2015-0204

MEDIUMCVSS v2 · 4.34.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.3 — 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:N/I:P/A:N. 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 98.7% 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
Elevated
4.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 99%
CISA-KEV: Not listedEPSS PROB: 99%CVSS v2: 4.3Exploit: Elevated riskExposed: 0

A fix is available — apply it.

The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k allows remote SSL servers to conduct RSA-to-EXPORT_RSA downgrade attacks and facilitate brute-force decryption by offering a weak ephemeral RSA key in a noncompliant role, related to the "FREAK" issue. NOTE: the scope of this CVE is only client code based on OpenSSL, not EXPORT_RSA issues associated with servers or other TLS implementations.

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

Published

January 9, 2015

Last Modified

May 6, 2026

References (132)

Vendor Advisories for CVE-2015-0204(2)

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
ubuntulibssl1.0.0 (1.0.1f-1ubuntu9.1) @ utopic2026-05-28ubuntu
redhatopenssl2016-08-22redhat
redhatpatch2015-05-13redhat
redhatpatch2015-04-16redhat
redhatopenssl-0:0.9.8e-33.el5_112015-04-13redhat
redhatopenssl-1:1.0.1e-34.el7_0.72015-01-21redhat

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.1k-1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.1k-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.1k-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
openssl—1.0.1k-1—
Debian:6.0(1)
PackageVulnerable rangeFixed inDependents
openssl0.9.8o-4 ... 0.9.8o-4squeeze9 (18 versions)0.9.8o-4squeeze19—
Debian:7(1)
PackageVulnerable rangeFixed inDependents
openssl1.0.1e-2 ... 1.0.1e-2+deb7u9 (14 versions)1.0.1e-2+deb7u14—

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

Publicly available exploits

(4 references)

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

  • GitHub PoCanthophilee/A2SV--SSL-VUL-Scan
    First seen Jan 1, 2021

    A2SV = Auto Scanning to SSL Vulnerability HeartBleed, CCS Injection, SSLv3 POODLE, FREAK... etc Support Vulnerability [CVE-2007-1858] Anonymous Cipher [CVE-2012-4929] CRIME(SPDY) [CVE-2014-0160] CCS Injection [CVE-2014-0224] HeartBleed [CVE-2014-3566] SSLv3 POODLE [CVE-2015-0204] FREAK Attack [CVE-2015-4000] LOGJAM Attack [CVE-2016-0800] SSLv2 DROWN Installation : $ apt update && apt upgrade $ apt install git $ apt install python2 $ apt install python $ git clone https://github.com/hahwul/ a2sv $ cd a2sv $ chmod +x * $ pip2 install -r requirements.txt usage : $ python2 a2sv.py -h It shows all commands how we can use this tool $ python a2sv.py -t 127.0.0.1 127.0.0.1 = target means here own device

    Open source ↗
  • GitHub PoCAbhishekGhosh/FREAK-Attack-CVE-2015-0204-Testing-Script
    First seen Mar 6, 2015

    Basic BASH Script to Automate OpenSSL based testing for FREAK Attack (CVE-2015-0204) as advised by Akamai.

    Open source ↗
  • GitHub PoCscottjpack/Freak-Scanner
    First seen Mar 5, 2015

    Multithreaded FREAK scanner, used to detect SSL EXP Ciphers, vulnerable to CVE-2015-0204

    Open source ↗
  • GitHub PoCfelmoltor/FreakVulnChecker
    First seen Mar 4, 2015

    This script check if your list of server is accepting Export cipher suites and could be vulnerable to CVE-2015-0204

    Open source ↗

Related CVEs(same vendor)

Frequently asked(4)

What is CVE-2015-0204?
CVE-2015-0204 is a medium vulnerability published on January 9, 2015. The ssl3getkeyexchange function in s3clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k allows remote SSL servers to conduct RSA-to-EXPORTRSA downgrade attacks and facilitate brute-force decryption by offering a weak ephemeral RSA key in a noncompliant role, related to…
When was CVE-2015-0204 disclosed?
CVE-2015-0204 was first published in the National Vulnerability Database on January 9, 2015, 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-2015-0204 actively exploited?
CVE-2015-0204 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99% probability of exploitation in the next 30 days, which ranks it in the top 0.1% of all scored CVEs.
How do I remediate CVE-2015-0204?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-0204, 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-2015-0204

Explore →

Is Your Infrastructure Affected by CVE-2015-0204?

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

Start Free Scan →Browse All CVEs