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

> Remote attackers can crash the OpenAFS client on Linux by sending a crafted RX response with a large error code, causing a null pointer dereference.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 9 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2009-1250, GHSA-cpqp-v482-xxhg

## What is CVE-2009-1250?

CVE-2009-1250 is a high-severity vulnerability in n/a, published on 9 Apr 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The cache manager in the client in OpenAFS 1.0 through 1.4.8 and 1.5.0 through 1.5.58, and IBM AFS 3.6 before Patch 19, on Linux allows remote attackers to cause a denial of service (system crash) via an RX response with a large error-code value that is interpreted as a pointer and dereferenced, related to use of the ERR_PTR macro.

Weakness: CWE-189

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

It affects 2 products.


Products: Ibm Afs, Openafs Openafs.

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

Upgrade to a fixed version.

## Is CVE-2009-1250 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2009-1250 is a high-severity vulnerability in n/a, published on 9 Apr 2009. 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-1250 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-2009-1250/ (Markdown: https://insights.sbomify.com/CVE-2009-1250/index.md)
```

## Sources

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

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