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

> Weak password hashing allows remote attackers to bypass authentication and access backup files in Retrospect software.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/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:** 21 Sep 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-wvjq-c28g-qpwg

## What is CVE-2015-2864?

CVE-2015-2864 is a medium-severity vulnerability in n/a, published on 21 Sep 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Retrospect and Retrospect Client before 10.0.2.119 on Windows, before 12.0.2.116 on OS X, and before 10.0.2.104 on Linux improperly generate password hashes, which makes it easier for remote attackers to bypass authentication and obtain access to backup files by leveraging a collision.

Weakness: CWE-255

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

It affects 2 products.


Products: Retrospect Retrospect, Retrospect Retrospect Client.

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

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

## Is CVE-2015-2864 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2864 is a medium-severity vulnerability in n/a, published on 21 Sep 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-2864 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-2864/ (Markdown: https://insights.sbomify.com/CVE-2015-2864/index.md)
```

## Sources

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

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