CVE-2015-2808

LOWNVD 3.7Elevated
3.7
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 74%
CISA-KEV: Not listedEPSS: 74%CVSS: 3.7Exploit: NoneExposed: 0

A fix is available — apply it.

The RC4 algorithm, as used in the TLS protocol and SSL protocol, does not properly combine state data with key data during the initialization phase, which makes it easier for remote attackers to conduct plaintext-recovery attacks against the initial bytes of a stream by sniffing network traffic that occasionally relies on keys affected by the Invariance Weakness, and then using a brute-force approach involving LSB values, aka the "Bar Mitzvah" issue.

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

Published

April 1, 2015

Last Modified

May 28, 2026

Advisory Details (3)

Auto-updated May 27, 2026
No patch confirmed yet.

Patch Availability(14)

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(1)

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

Additional Vendor Advisories

(3)

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

Frequently asked(5)

What is CVE-2015-2808?
CVE-2015-2808 is a low vulnerability published on April 1, 2015. The RC4 algorithm, as used in the TLS protocol and SSL protocol, does not properly combine state data with key data during the initialization phase, which makes it easier for remote attackers to conduct plaintext-recovery attacks against the initial bytes of a stream by sniffing network traffic…
When was CVE-2015-2808 disclosed?
CVE-2015-2808 was first published in the National Vulnerability Database on April 1, 2015, with the most recent update on May 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2015-2808 actively exploited?
CVE-2015-2808 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.
What is the CVSS score of CVE-2015-2808?
CVE-2015-2808 has a CVSS v3 base score of 3.7 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 0.0.
How do I remediate CVE-2015-2808?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2015-2808, 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-2808

Explore →

Is Your Infrastructure Affected by CVE-2015-2808?

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