# CVE-2001-0073: Memory corruption in n/a

> A buffer overflow in the SELinux library allows attackers to modify critical memory data, potentially compromising system integrity.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** No
- **Published:** 2 Feb 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hv5v-h4qh-vgxj

## What is CVE-2001-0073?

CVE-2001-0073 is a low-severity memory corruption vulnerability in n/a, published on 2 Feb 2001. 

### Official description

Buffer overflow in the find_default_type function in libsecure in NSA Security-enhanced Linux, which may allow attackers to modify critical data in memory.

## Which versions are affected by CVE-2001-0073?

It affects 1 product.


Products: Nsa Security-Enhanced Linux.

## How do I fix CVE-2001-0073?

No fix has been published for CVE-2001-0073 yet. Limit exposure of the affected software until one is available.

## Is CVE-2001-0073 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0073 and fix it if it is affected.

What it is: CVE-2001-0073 is a low-severity memory corruption vulnerability in n/a, published on 2 Feb 2001. 
Exploitation: There is no known exploitation of CVE-2001-0073 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-2001-0073/ (Markdown: https://insights.sbomify.com/CVE-2001-0073/index.md)
```

## Sources

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

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