CVE-2015-28083.7LowCWE-327

CVE-2015-2808

Vendor not named in the CVE record

Vendor fix available · Exploitation: likely to be exploited (10% or more)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

73.8%probability of exploitation in the next 30 days

99th percentile

050100

Higher than 99% of scored CVEs

3.7LowCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Likely to be exploited (10% or more). EPSS gives it a 10% or higher chance of exploitation in the next 30 days.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Use of a Broken or Risky Cryptographic Algorithm · Cryptography
Published: April 2015
Band: Likely to be exploited (10% or more), April 2015

CoverageNo articles yet

No CyberSIXT article names CVE-2015-2808 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References

28 more references are in the CVE record.