# CVE-2011-0430: Use after free in n/a

> Remote attackers can execute arbitrary code or cause denial of service in OpenAFS Rx server via a double free vulnerability.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Feb 2011
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2011-0430, GHSA-w7w2-q5r2-ccx8

## What is CVE-2011-0430?

CVE-2011-0430 is a high-severity use after free vulnerability in n/a, published on 18 Feb 2011. It can be exploited over the network, with no action from the victim.

### Official description

Double free vulnerability in the Rx server process in OpenAFS 1.4.14, 1.4.12, 1.4.7, and possibly other versions allows remote attackers to cause a denial of service and execute arbitrary code via unknown vectors.

Weakness: CWE-399

## Which versions are affected by CVE-2011-0430?

It affects 1 product.


Products: Openafs Openafs.

## How do I fix CVE-2011-0430?

Upgrade to a fixed version.

## Is CVE-2011-0430 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-1251](https://insights.sbomify.com/CVE-2009-1251/): Memory corruption in n/a (critical 10.0)
- [CVE-2024-10394](https://insights.sbomify.com/CVE-2024-10394/): Theft of credentials in Unix client PAGs (high 8.4)
- [CVE-2024-10397](https://insights.sbomify.com/CVE-2024-10397/): Preallocated buffer overflows in XDR responses (high 7.7)
- [CVE-2019-18601](https://insights.sbomify.com/CVE-2019-18601/): Denial of service in n/a (high 7.5)
- [CVE-2007-1507](https://insights.sbomify.com/CVE-2007-1507/): Privilege escalation in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-0430 and fix it if it is affected.

What it is: CVE-2011-0430 is a high-severity use after free vulnerability in n/a, published on 18 Feb 2011. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-0430 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-2011-0430/ (Markdown: https://insights.sbomify.com/CVE-2011-0430/index.md)
```

## Sources

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

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