# CVE-2012-0060: Memory corruption in n/a

> Remote attackers can cause crashes or execute arbitrary code by providing a malicious RPM package header with invalid region tags.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 4 Jun 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-0060, GHSA-j6wj-cqmg-hvcm

## What is CVE-2012-0060?

CVE-2012-0060 is a medium-severity memory corruption vulnerability in n/a, published on 4 Jun 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

RPM before 4.9.1.3 does not properly validate region tags, which allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via an invalid region tag in a package header to the (1) headerLoad, (2) rpmReadSignature, or (3) headerVerify function.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2012-0060?

It affects 1 product.


Products: Rpm Rpm.

## How do I fix CVE-2012-0060?

Upgrade to a fixed version.

## Is CVE-2012-0060 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-8118](https://insights.sbomify.com/CVE-2014-8118/): Integer overflow in n/a (critical 10.0)
- [CVE-2011-3378](https://insights.sbomify.com/CVE-2011-3378/): Memory corruption in n/a (critical 9.3)
- [CVE-2017-7501](https://insights.sbomify.com/CVE-2017-7501/): Path traversal in rpm (high 7.8)
- [CVE-2017-7500](https://insights.sbomify.com/CVE-2017-7500/): Path traversal in rpm (high 7.3)
- [CVE-2005-4889](https://insights.sbomify.com/CVE-2005-4889/): Race condition in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0060 and fix it if it is affected.

What it is: CVE-2012-0060 is a medium-severity memory corruption vulnerability in n/a, published on 4 Jun 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2012-0060 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-2012-0060/ (Markdown: https://insights.sbomify.com/CVE-2012-0060/index.md)
```

## Sources

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

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