# CVE-2003-0147: Information disclosure in n/a

> Attackers can recover private keys via timing side-channels because RSA blinding is disabled by default in OpenSSL.

- **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:** 18 Mar 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0147, GHSA-4q57-g9fh-w67x

## What is CVE-2003-0147?

CVE-2003-0147 is a medium-severity vulnerability in Openssl Openssl, published on 18 Mar 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenSSL does not use RSA blinding by default, which allows local and remote attackers to obtain the server's private key by determining factors using timing differences on (1) the number of extra reductions during Montgomery reduction, and (2) the use of different integer multiplication algorithms ("Karatsuba" and normal).

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

It affects 3 products.


Products: Openpkg Openpkg, Openssl Openssl, Stunnel Stunnel.

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

Change a configuration setting.

## Is CVE-2003-0147 being exploited?

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

## Other vulnerabilities in Openssl Openssl

- [CVE-2004-1019](https://insights.sbomify.com/CVE-2004-1019/): Deserialization in n/a (critical 10.0)
- [CVE-2004-1065](https://insights.sbomify.com/CVE-2004-1065/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0413](https://insights.sbomify.com/CVE-2004-0413/): Integer overflow in n/a (critical 10.0)
- [CVE-2002-0985](https://insights.sbomify.com/CVE-2002-0985/): Command injection in n/a (high 7.5)
- [CVE-2004-0957](https://insights.sbomify.com/CVE-2004-0957/): Privilege escalation in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0147 is a medium-severity vulnerability in Openssl Openssl, published on 18 Mar 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-0147 in the wild and no public exploit code.

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

## Sources

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

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