Security readout for executives and security teams
CVE-2015-2808 is the RC4 "Bar Mitzvah" weakness in TLS/SSL. It can help a network attacker recover small amounts of early plaintext from traffic when RC4 is negotiated. The practical risk is mainly legacy exposure: systems that still allow RC4 cipher suites. Exposure is likely limited to legacy servers, clients, appliances, or middleware still permitting RC4 in TLS/SSL. The CVE bundle does not identify a single affected product family; it references multiple vendor advisories, so asset-specific vendor mapping is required. Treat this as a legacy cryptography cleanup item, not an emergency incident based on provided evidence. Prioritize internet-facing systems and regulated environments where weak encryption findings affect audit, customer trust, or data protection commitments. Mitigation focus: Identify TLS/SSL services that still allow RC4 cipher suites.; Disable RC4 where vendor-supported and prefer modern TLS cipher suites.; Apply relevant vendor guidance from Red Hat, HPE, Oracle, Juniper, SUSE, IBM, or Gentoo..
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-327: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2015-2808 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N2.21.4CISA-ADPVulnerability scoring details
Base CVSS 3.1 score
3.7LowVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://h20564.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c04773256CVE reference, mitre
- https://kb.juniper.net/JSA10783CVE reference, mitre
- GLSA-201512-10CVE reference, mitre · vendor-advisory
- https://h20566.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04708650CVE reference, mitre
- https://h20564.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c04772190CVE reference, mitre
- https://h20566.www2.hpe.com/hpsc/doc/public/display?docId=emr_na-c04711380CVE reference, mitre
- https://kc.mcafee.com/corporate/index?page=content&id=SB10163CVE reference, mitre
- https://h20566.www2.hpe.com/portal/site/hpsc/public/kb/docDisplay?docId=emr_na-c05193347CVE reference, mitre
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of a Broken or Risky Cryptographic Algorithm
Use of a Broken or Risky Cryptographic Algorithm represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.