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

> Remote attackers can obtain sensitive information due to the use of the vulnerable RC4 cipher in TLS connections.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** No
- **Published:** 4 Feb 2020
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-3fmj-978w-qxm2

## What is CVE-2015-2802?

CVE-2015-2802 is a high-severity vulnerability in n/a, published on 4 Feb 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Information Disclosure vulnerability exists in HP SiteScope 11.2 and 11.3 on Windows, Linux and Solaris, HP Asset Manager 9.30 through 9.32, 9.40 through 9.41, 9.50, and Asset Manager Cloudsystem Chargeback 9.40, which could let a remote malicious user obtain sensitive information. This is the TLS vulnerability known as the RC4 cipher Bar Mitzvah vulnerability.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 3 products.


Products: Hp Asset Manager, Hp Asset Manager Cloudsystem Chargeback, Hp Sitescope.

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

No fix has been published for CVE-2015-2802 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-2802 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-2000](https://insights.sbomify.com/CVE-2016-2000/): Deserialization in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2802 is a high-severity vulnerability in n/a, published on 4 Feb 2020. 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-2802 in the wild and no public exploit code.

Affected product: n/a. 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-2802/ (Markdown: https://insights.sbomify.com/CVE-2015-2802/index.md)
```

## Sources

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

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