# CVE-2015-2808: Weak cryptography in n/a

> Remote attackers can recover plaintext from TLS/SSL streams using RC4 due to initialization flaws, requiring disabling RC4 ciphers.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Apr 2015
- **Updated:** 28 May 2026
- **Also known as:** GHSA-jcj6-c96p-jcmm, UBUNTU-CVE-2015-2808

## What is CVE-2015-2808?

CVE-2015-2808 is a low-severity vulnerability in Canonical Ubuntu Linux, published on 1 Apr 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2015-2808?

It affects 61 products.


Products: Canonical Ubuntu Linux, Debian Debian Linux, Fujitsu Sparc Enterprise M3000 Firmware, Fujitsu Sparc Enterprise M4000 Firmware, Fujitsu Sparc Enterprise M5000 Firmware, Fujitsu Sparc Enterprise M8000 Firmware, Fujitsu Sparc Enterprise M9000 Firmware, Huawei 9700 Firmware, Huawei E6000 Firmware, Huawei E9000 Firmware, Huawei Oceanstor 18500 Firmware, Huawei Oceanstor 18800 Firmware, Huawei Oceanstor 18800f Firmware, Huawei Oceanstor 9000 Firmware, Huawei Oceanstor Cse Firmware, Huawei Oceanstor Hvs85t Firmware, Huawei Oceanstor Replicationdirector, Huawei Oceanstor S2600t Firmware, Huawei Oceanstor S5500t Firmware, Huawei Oceanstor S5600t Firmware and 41 more.

## How do I fix CVE-2015-2808?

Change a configuration setting.

## Is CVE-2015-2808 being exploited?

There is no known exploitation of CVE-2015-2808 in the wild and no public exploit code.

## Other vulnerabilities in Canonical Ubuntu Linux

- [CVE-2020-11651](https://insights.sbomify.com/CVE-2020-11651/): SaltStack Salt Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2020-7247](https://insights.sbomify.com/CVE-2020-7247/): OpenSMTPD Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2019-16928](https://insights.sbomify.com/CVE-2019-16928/): Exim Out-of-bounds Write (critical 9.8, exploited in the wild)
- [CVE-2018-6789](https://insights.sbomify.com/CVE-2018-6789/): Exim Buffer Overflow (critical 9.8, exploited in the wild)
- [CVE-2015-2590](https://insights.sbomify.com/CVE-2015-2590/): Oracle Java SE and Java SE Embedded Remote Code Execution (critical 9.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2808 and fix it if it is affected.

What it is: CVE-2015-2808 is a low-severity vulnerability in Canonical Ubuntu Linux, published on 1 Apr 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-2808 in the wild and no public exploit code.

Affected product: Canonical Ubuntu Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-2808/ (Markdown: https://insights.sbomify.com/CVE-2015-2808/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-2808
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-2808
- OSV: https://osv.dev/vulnerability/CVE-2015-2808

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-2808/
Summaries are generated and may contain mistakes; the official description above is the record.