CVE-2011-3389

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 73%
CISA-KEV: Not listedEPSS: 73%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP headers via a blockwise chosen-boundary attack (BCBA) on an HTTPS session, in conjunction with JavaScript code that uses (1) the HTML5 WebSocket API, (2) the Java URLConnection API, or (3) the Silverlight WebClient API, aka a "BEAST" attack.

CVSS v3
—
EG Score
0.0(none)
EPSS
99.4%
KEV
Not listed

Published

September 6, 2011

Last Modified

April 29, 2026

References (178)

Vendor Advisories for CVE-2011-3389(7)

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

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntuopenjdk-6-jre-lib (6b23~pre11-0ubuntu1.11.10) @ oneiric2026-05-29ubuntu
redhatjava-1.6.0-ibm-1:1.6.0.14.0-1jpp.1.el5_92013-10-23redhat
redhatjava-1.5.0-ibm-1:1.5.0.13.1-1jpp.2.el6_22012-04-23redhat
redhatjava-1.4.2-ibm-sap-0:1.4.2.13.11.sap-1jpp.1.el52012-02-29redhat
redhatjava-1.6.0-ibm-1:1.6.0.10.0-1jpp.2.el52012-01-18redhat
redhatjava-1.4.2-ibm-0:1.4.2.13.11-1jpp.1.el52012-01-09redhat
redhatjava-1.6.0-sun-1:1.6.0.29-1jpp.1.el52011-10-19redhat
redhatjava-1.6.0-openjdk-1:1.6.0.0-1.40.1.9.10.el6_12011-10-18redhat

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.

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 8× in last 7d / 24× 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-22 14:03 UTCEPSS rescore
  2. 2026-07-21 15:21 UTCEPSS rescore
  3. 2026-07-20 17:03 UTCEPSS rescore
  4. 2026-07-20 17:03 UTCEPSS rescore
  5. 2026-07-19 02:25 UTCEPSS rescore
  6. 2026-07-19 02:25 UTCEPSS rescore
  7. 2026-07-18 10:00 UTCEPSS rescore
  8. 2026-07-16 16:58 UTCEPSS rescore
  9. 2026-07-15 16:54 UTCEPSS rescore
  10. 2026-07-15 16:54 UTCEPSS rescore
  11. 2026-07-13 06:08 UTCEPSS rescore
  12. 2026-07-08 15:10 UTCEPSS rescore
  13. 2026-07-08 15:10 UTCEPSS rescore
  14. 2026-07-06 16:23 UTCEPSS rescore
  15. 2026-07-05 18:59 UTCOSV refresh
  16. 2026-07-05 02:26 UTCEPSS rescore
  17. 2026-07-01 15:02 UTCEPSS rescore
  18. 2026-07-01 15:02 UTCEPSS rescore
  19. 2026-06-30 23:19 UTCEPSS rescore
  20. 2026-06-30 23:19 UTCEPSS rescore
  21. 2026-06-29 14:02 UTCEPSS rescore
  22. 2026-06-25 13:46 UTCEPSS rescore
  23. 2026-06-23 21:30 UTCEPSS rescore
  24. 2026-06-23 21:30 UTCEPSS rescore
  25. 2026-06-17 17:49 UTCEPSS rescore
Show 54 more
  1. 2026-06-17 17:49 UTCEPSS rescore
  2. 2026-06-17 17:49 UTCEPSS rescore
  3. 2026-06-17 06:05 UTCOSV refresh
  4. 2026-06-15 17:44 UTCEPSS rescore
  5. 2026-06-13 22:57 UTCEPSS rescore
  6. 2026-06-13 22:57 UTCEPSS rescore
  7. 2026-06-12 23:08 UTCEPSS rescore
  8. 2026-06-11 13:56 UTCEPSS rescore
  9. 2026-06-10 22:14 UTCEPSS rescore
  10. 2026-06-10 13:17 UTCEPSS rescore
  11. 2026-06-07 15:22 UTCEPSS rescore
  12. 2026-06-07 15:22 UTCEPSS rescore
  13. 2026-06-06 13:45 UTCEPSS rescore
  14. 2026-06-06 13:44 UTCEPSS rescore
  15. 2026-06-05 22:44 UTCEPSS rescore
  16. 2026-06-05 06:08 UTCEPSS rescore
  17. 2026-06-05 06:07 UTCEPSS rescore
  18. 2026-06-04 13:09 UTCEPSS rescore
  19. 2026-06-04 13:09 UTCEPSS rescore
  20. 2026-06-02 20:10 UTCEPSS rescore
  21. 2026-06-02 20:10 UTCEPSS rescore
  22. 2026-06-01 13:49 UTCEPSS rescore
  23. 2026-06-01 13:49 UTCEPSS rescore
  24. 2026-05-31 22:28 UTCEPSS rescore
  25. 2026-05-31 22:28 UTCEPSS rescore
  26. 2026-05-31 00:14 UTCEPSS rescore
  27. 2026-05-31 00:14 UTCEPSS rescore
  28. 2026-05-29 13:41 UTCEPSS rescore
  29. 2026-05-29 13:40 UTCEPSS rescore
  30. 2026-05-29 07:06 UTCEG score recompute
  31. 2026-05-29 07:06 UTCVendor advisory
  32. 2026-05-29 07:06 UTCGHSA enrichment
  33. 2026-05-28 13:42 UTCEPSS rescore
  34. 2026-05-28 13:42 UTCEPSS rescore
  35. 2026-05-28 13:42 UTCEPSS rescore
  36. 2026-05-27 13:38 UTCEPSS rescore
  37. 2026-05-27 13:38 UTCEPSS rescore
  38. 2026-05-26 13:41 UTCEPSS rescore
  39. 2026-05-26 13:41 UTCEPSS rescore
  40. 2026-05-26 07:16 UTCEPSS rescore
  41. 2026-05-26 07:16 UTCEPSS rescore
  42. 2026-05-24 16:43 UTCEPSS rescore
  43. 2026-05-23 22:05 UTCOSV refresh
  44. 2026-05-22 21:15 UTCEPSS rescore
  45. 2026-05-22 21:15 UTCEPSS rescore
  46. 2026-05-22 21:15 UTCEPSS rescore
  47. 2026-05-20 22:37 UTCEPSS rescore
  48. 2026-05-20 22:37 UTCEPSS rescore
  49. 2026-05-20 22:37 UTCEPSS rescore
  50. 2026-05-20 11:21 UTCEPSS rescore
  51. 2026-05-20 11:21 UTCEPSS rescore
  52. 2026-05-20 11:21 UTCEPSS rescore
  53. 2026-05-18 21:29 UTCEPSS rescore
  54. 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 PoCmpgn/BEAST-PoC
    First seen Mar 28, 2015

    :muscle: Proof Of Concept of the BEAST attack against SSL/TLS CVE-2011-3389 :muscle:

    Open source ↗
  • Metasploitauxiliary/scanner/ssl/ssl_version✓ verified
    First seen Oct 14, 2014

    SSL/TLS Version Detection

    Open source ↗

Related CVEs(same vendor + same CWE)

Frequently asked(4)

What is CVE-2011-3389?
CVE-2011-3389 is a none vulnerability published on September 6, 2011. The SSL protocol, as used in certain configurations in Microsoft Windows and Microsoft Internet Explorer, Mozilla Firefox, Google Chrome, Opera, and other products, encrypts data by using CBC mode with chained initialization vectors, which allows man-in-the-middle attackers to obtain plaintext HTTP…
When was CVE-2011-3389 disclosed?
CVE-2011-3389 was first published in the National Vulnerability Database on September 6, 2011, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2011-3389 actively exploited?
CVE-2011-3389 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2011-3389?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2011-3389, 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-2011-3389

Explore →

Is Your Infrastructure Affected by CVE-2011-3389?

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

Start Free Scan →Browse All CVEs