# CVE-2015-2141: Information disclosure in n/a

> Remote attackers can obtain private keys via timing attacks due to improper blinding in the Rabin-Williams signature algorithm.

- **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:** Yes
- **Published:** 1 Jul 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-2141, DLA-262-1, DSA-3296-1, GHSA-xm6q-j5wx-7362, MGASA-2015-0317, UBUNTU-CVE-2015-2141, openSUSE-SU-2024:10336-1

## What is CVE-2015-2141?

CVE-2015-2141 is a medium-severity vulnerability in Opensuse Opensuse, published on 1 Jul 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The InvertibleRWFunction::CalculateInverse function in rw.cpp in libcrypt++ 5.6.2 does not properly blind private key operations for the Rabin-Williams digital signature algorithm, which allows remote attackers to obtain private keys via a timing attack.

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

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libcryptopp` | openSUSE:Tumbleweed | All versions | 5.6.4-1.3 |

Products: Cryptopp Crypto\+\+ Library, Opensuse Opensuse.

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

Upgrade to a fixed version.

## Is CVE-2015-2141 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2141 is a medium-severity vulnerability in Opensuse Opensuse, published on 1 Jul 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-2141 in the wild and no public exploit code.

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

## Sources

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

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