# CVE-2009-3245: Null dereference in n/a

> A missing NULL check in OpenSSL's big number expansion functions can lead to a null pointer dereference, potentially causing a denial of service.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Mar 2010
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-3245, GHSA-c5qh-p8w9-vjq7, RHSA-2010:0173

## What is CVE-2009-3245?

CVE-2009-3245 is a critical vulnerability in Openssl Openssl, published on 5 Mar 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OpenSSL before 0.9.8m does not check for a NULL return value from bn_wexpand function calls in (1) crypto/bn/bn_div.c, (2) crypto/bn/bn_gf2m.c, (3) crypto/ec/ec2_smpl.c, and (4) engines/e_ubsec.c, which has unspecified impact and context-dependent attack vectors.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2009-3245?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `openssl096b` | Red Hat:enterprise_linux:3::as | All versions | 0:0.9.6b-16.50 |
| `openssl096b-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 0:0.9.6b-16.50 |
| `openssl096b` | Red Hat:enterprise_linux:3::desktop | All versions | 0:0.9.6b-16.50 |
| `openssl096b-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 0:0.9.6b-16.50 |
| `openssl096b` | Red Hat:enterprise_linux:3::es | All versions | 0:0.9.6b-16.50 |
| `openssl096b-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 0:0.9.6b-16.50 |
| `openssl096b` | Red Hat:enterprise_linux:3::ws | All versions | 0:0.9.6b-16.50 |
| `openssl096b-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 0:0.9.6b-16.50 |
| `openssl096b` | Red Hat:enterprise_linux:4::as | All versions | 0:0.9.6b-22.46.el4_8.1 |
| `openssl096b-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:0.9.6b-22.46.el4_8.1 |
| `openssl096b` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.9.6b-22.46.el4_8.1 |
| `openssl096b-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:0.9.6b-22.46.el4_8.1 |
| `openssl096b` | Red Hat:enterprise_linux:4::es | All versions | 0:0.9.6b-22.46.el4_8.1 |
| `openssl096b-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:0.9.6b-22.46.el4_8.1 |
| `openssl096b` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.9.6b-22.46.el4_8.1 |
| `openssl096b-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:0.9.6b-22.46.el4_8.1 |

Products: Openssl Openssl.

## How do I fix CVE-2009-3245?

Upgrade to a fixed version.

## Is CVE-2009-3245 being exploited?

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

## Other vulnerabilities in Openssl Openssl

- [CVE-2006-3738](https://insights.sbomify.com/CVE-2006-3738/): Memory corruption in n/a (critical 10.0)
- [CVE-2026-63073](https://insights.sbomify.com/CVE-2026-63073/): Untrusted Sender DN Used as Format String in CMP Response Validation (critical 9.8)
- [CVE-2016-6309](https://insights.sbomify.com/CVE-2016-6309/): Use after free in n/a (critical 9.8)
- [CVE-2016-0799](https://insights.sbomify.com/CVE-2016-0799/): Integer overflow in n/a (critical 9.8)
- [CVE-2016-2842](https://insights.sbomify.com/CVE-2016-2842/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-3245 and fix it if it is affected.

What it is: CVE-2009-3245 is a critical vulnerability in Openssl Openssl, published on 5 Mar 2010. 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-2009-3245 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-2009-3245/ (Markdown: https://insights.sbomify.com/CVE-2009-3245/index.md)
```

## Sources

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

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