CVE-2015-2808

CRITICALNVD 3.710.0▲
EchelonGraph scoreMEDIUM confidence

Score 10.0 from GitHub Security Advisory published 2022-05-13. NVD baseline CVSS 3.7; sources differ by 6.3.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
10.0EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 74%
CISA-KEV: Not listedEPSS PROB: 74%CVSS: 3.7Exploit: Elevated riskExposed services: Not assessed

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
10.0CRITICALmedium confidence
EG Risk
75
EG Risk 75/100CISA SSVC

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
Severity100% × 45%
Exploitation74% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
74%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 1, 2015

Last Modified

May 28, 2026

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.

Affected Packages

(4 across 3 ecosystems)
Debian:7(2)
PackageVulnerable rangeFix by version rangeDependents
openjdk-66b27-1.12.5-1 ... 6b36-1.13.8-1~deb6u1 (32 versions)
  • every version up to 6b36-1.13.8-1~deb7u1: fixed in 6b36-1.13.8-1~deb7u1
—
openjdk-77u13-2.3.6-1 ... 7u9-2.3.5~pre1-1 (66 versions)
  • every version up to 7u79-2.5.6-1~deb7u1: fixed in 7u79-2.5.6-1~deb7u1
—
Debian:6.0(1)
PackageVulnerable rangeFix by version rangeDependents
openjdk-66b18-1.8.10-0+squeeze1 ... 6b35-1.13.7-1~deb7u1 (102 versions)
  • every version up to 6b36-1.13.8-1~deb6u1: fixed in 6b36-1.13.8-1~deb6u1
—
Debian:8(1)
PackageVulnerable rangeFix by version rangeDependents
openjdk-77u75-2.5.4-2 ... 7u79-2.5.6-1~deb7u1 (6 versions)
  • every version up to 7u79-2.5.6-1~deb8u1: fixed in 7u79-2.5.6-1~deb8u1
—

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 2× in last 7d / 11× 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.

Showing the most recent 100 of 102 total refreshes for this CVE.

  1. 2026-10-07 23:40 UTCEPSS rescore
  2. 2026-10-06 15:11 UTCEPSS rescore
  3. 2026-10-03 14:21 UTCEPSS rescore
  4. 2026-09-30 14:58 UTCEPSS rescore
  5. 2026-09-30 09:03 UTCEG score recompute
  6. 2026-09-27 13:40 UTCEPSS rescore
  7. 2026-09-27 13:40 UTCEPSS rescore
  8. 2026-09-18 19:22 UTCEPSS rescore
  9. 2026-09-17 19:21 UTCEPSS rescore
  10. 2026-09-12 14:55 UTCEPSS rescore
  11. 2026-09-11 09:31 UTCEPSS rescore
  12. 2026-09-10 09:26 UTCEPSS rescore
  13. 2026-09-06 13:42 UTCEPSS rescore
  14. 2026-09-05 15:23 UTCEPSS rescore
  15. 2026-09-04 13:55 UTCEPSS rescore
  16. 2026-09-02 14:07 UTCEPSS rescore
  17. 2026-08-30 19:12 UTCEPSS rescore
  18. 2026-08-26 14:41 UTCEPSS rescore
  19. 2026-08-21 23:44 UTCEPSS rescore
  20. 2026-08-19 16:59 UTCEPSS rescore
  21. 2026-08-16 02:09 UTCEPSS rescore
  22. 2026-08-15 01:25 UTCEPSS rescore
  23. 2026-08-12 13:46 UTCEPSS rescore
  24. 2026-08-09 13:42 UTCEPSS rescore
  25. 2026-08-07 16:22 UTCEPSS rescore
Show 75 more
  1. 2026-08-05 19:12 UTCEPSS rescore
  2. 2026-07-30 16:23 UTCEPSS rescore
  3. 2026-07-28 15:31 UTCEPSS rescore
  4. 2026-07-24 14:13 UTCEPSS rescore
  5. 2026-07-23 01:17 UTCEG score recompute
  6. 2026-07-23 00:19 UTCEG score recompute
  7. 2026-07-22 21:58 UTCEG score recompute
  8. 2026-07-22 14:04 UTCEPSS rescore
  9. 2026-07-21 15:21 UTCEPSS rescore
  10. 2026-07-21 15:21 UTCEPSS rescore
  11. 2026-07-20 17:03 UTCEPSS rescore
  12. 2026-07-19 14:27 UTCEPSS rescore
  13. 2026-07-19 14:27 UTCEPSS rescore
  14. 2026-07-17 06:51 UTCEG score recompute▲ 10.00
  15. 2026-07-17 06:51 UTCVendor advisory
  16. 2026-07-17 06:50 UTCGHSA enrichment
  17. 2026-07-15 16:54 UTCEPSS rescore
  18. 2026-07-15 16:54 UTCEPSS rescore
  19. 2026-07-13 22:26 UTCEPSS rescore
  20. 2026-07-11 08:23 UTCEPSS rescore
  21. 2026-07-09 19:05 UTCEPSS rescore
  22. 2026-07-05 02:26 UTCEPSS rescore
  23. 2026-07-02 15:21 UTCEPSS rescore
  24. 2026-07-01 15:02 UTCEPSS rescore
  25. 2026-07-01 15:02 UTCEPSS rescore
  26. 2026-06-27 03:05 UTCEPSS rescore
  27. 2026-06-25 13:47 UTCEPSS rescore
  28. 2026-06-25 13:47 UTCEPSS rescore
  29. 2026-06-24 14:02 UTCEPSS rescore
  30. 2026-06-24 14:02 UTCEPSS rescore
  31. 2026-06-23 21:30 UTCEPSS rescore
  32. 2026-06-21 14:54 UTCEPSS rescore
  33. 2026-06-18 17:50 UTCEPSS rescore
  34. 2026-06-18 17:49 UTCEPSS rescore
  35. 2026-06-16 17:50 UTCEPSS rescore
  36. 2026-06-16 17:49 UTCEPSS rescore
  37. 2026-06-15 17:45 UTCEPSS rescore
  38. 2026-06-14 23:14 UTCEPSS rescore
  39. 2026-06-13 22:57 UTCEPSS rescore
  40. 2026-06-12 23:09 UTCEPSS rescore
  41. 2026-06-11 13:57 UTCEPSS rescore
  42. 2026-06-10 22:15 UTCEPSS rescore
  43. 2026-06-06 13:45 UTCEPSS rescore
  44. 2026-06-05 22:44 UTCEPSS rescore
  45. 2026-06-05 06:08 UTCEPSS rescore
  46. 2026-06-05 06:08 UTCEPSS rescore
  47. 2026-06-04 13:10 UTCEPSS rescore
  48. 2026-06-04 13:09 UTCEPSS rescore
  49. 2026-06-02 20:10 UTCEPSS rescore
  50. 2026-06-02 20:10 UTCEPSS rescore
  51. 2026-06-01 13:49 UTCEPSS rescore
  52. 2026-06-01 13:49 UTCEPSS rescore
  53. 2026-05-31 00:14 UTCEPSS rescore
  54. 2026-05-29 13:41 UTCEPSS rescore
  55. 2026-05-28 13:42 UTCEPSS rescore
  56. 2026-05-28 13:42 UTCEPSS rescore
  57. 2026-05-27 13:38 UTCEPSS rescore
  58. 2026-05-27 13:38 UTCEPSS rescore
  59. 2026-05-26 13:41 UTCEPSS rescore
  60. 2026-05-26 13:41 UTCEPSS rescore
  61. 2026-05-26 07:16 UTCEPSS rescore
  62. 2026-05-26 07:16 UTCEPSS rescore
  63. 2026-05-24 16:43 UTCEPSS rescore
  64. 2026-05-23 15:10 UTCEPSS rescore
  65. 2026-05-23 02:03 UTCEG score recompute
  66. 2026-05-23 02:03 UTCVendor advisory
  67. 2026-05-23 02:03 UTCGHSA enrichment
  68. 2026-05-22 21:15 UTCEPSS rescore
  69. 2026-05-22 21:15 UTCEPSS rescore
  70. 2026-05-21 22:40 UTCEPSS rescore
  71. 2026-05-20 22:37 UTCEPSS rescore
  72. 2026-05-20 22:37 UTCEPSS rescore
  73. 2026-05-20 11:21 UTCEPSS rescore
  74. 2026-05-20 11:21 UTCEPSS rescore
  75. 2026-05-20 11:21 UTCEPSS rescore

Frequently asked(5)

What is CVE-2015-2808?
CVE-2015-2808 is a critical 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 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 74% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
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 10.0 (CRITICAL).
How do I remediate CVE-2015-2808?
A fix for CVE-2015-2808 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2015-2808 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.