# CVE-2003-0971: Weak cryptography in n/a

> Attackers can recover private keys from signatures due to flawed ElGamal key generation in GnuPG, compromising encrypted data confidentiality.

- **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:** 2 Dec 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-429, GHSA-3rmj-3mrh-fv5j, RHSA-2003:395

## What is CVE-2003-0971?

CVE-2003-0971 is a medium-severity vulnerability in n/a, published on 2 Dec 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

GnuPG (GPG) 1.0.2, and other versions up to 1.2.3, creates ElGamal type 20 (sign+encrypt) keys using the same key component for encryption as for signing, which allows attackers to determine the private key from a signature.

## Which versions are affected by CVE-2003-0971?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `gnupg` | Red Hat:enterprise_linux:3::as | All versions | 0:1.2.1-10 |
| `gnupg-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:1.2.1-10 |
| `gnupg` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.2.1-10 |
| `gnupg-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:1.2.1-10 |
| `gnupg` | Red Hat:enterprise_linux:3::es | All versions | 0:1.2.1-10 |
| `gnupg-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:1.2.1-10 |
| `gnupg` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.2.1-10 |
| `gnupg-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:1.2.1-10 |

Products: Gnu Privacy Guard.

## How do I fix CVE-2003-0971?

Upgrade to a fixed version.

## Is CVE-2003-0971 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-6235](https://insights.sbomify.com/CVE-2006-6235/): Use after free in n/a (critical 10.0)
- [CVE-2003-0255](https://insights.sbomify.com/CVE-2003-0255/): Security feature bypass in n/a (critical 10.0)
- [CVE-2003-0978](https://insights.sbomify.com/CVE-2003-0978/): Memory corruption in n/a (high 7.5)
- [CVE-2001-0522](https://insights.sbomify.com/CVE-2001-0522/): Memory corruption in n/a (high 7.5)
- [CVE-2000-0974](https://insights.sbomify.com/CVE-2000-0974/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0971 and fix it if it is affected.

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

## Sources

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

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