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

> Weak encryption in Azure Linux allows attackers to recover plaintext from small files via differential cryptanalysis.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** AZL-34660, AZL-6376, GHSA-r8gg-jrgv-562w

## What is CVE-2015-2987?

CVE-2015-2987 is a low-severity vulnerability in n/a, published on 28 Aug 2015. 

### Official description

Type74 ED before 4.0 misuses 128-bit ECB encryption for small files, which makes it easier for attackers to obtain plaintext data via differential cryptanalysis of a file with an original length smaller than 128 bits.

Weakness: CWE-17

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

It affects 1 product.


Products: Type74 Ed.

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

Upgrade to a fixed version.

## Is CVE-2015-2987 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2987 is a low-severity vulnerability in n/a, published on 28 Aug 2015. 
Exploitation: There is no known exploitation of CVE-2015-2987 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-2987/ (Markdown: https://insights.sbomify.com/CVE-2015-2987/index.md)
```

## Sources

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

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