CVE-2015-0204

NONECVSS 0.09.0
EchelonGraph scoreLOW confidence

Score elevated to 9.0 because EPSS predicts 92% probability of exploitation within the next 30 days (top 0.3% of all CVEs). Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss
Elevated
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 99%
CISA-KEV: Not listedEPSS: 99%CVSS: Exploit: NoneExposed: 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 v3
EG Score
9.0(low)
EPSS
99.9%
KEV
Not listed

Published

January 9, 2015

Last Modified

May 6, 2026

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.

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

Frequently asked(4)

What is CVE-2015-0204?
CVE-2015-0204 is a none 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.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
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

Explore the affected products and dependency analysis for 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.