# CVE-2012-6119: Security feature bypass in n/a

> Local attackers can bypass manifest signature checks to modify subscription manifests in Candlepin and Red Hat Subscription Asset Manager.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jffh-2rxm-9wjg

## What is CVE-2012-6119?

CVE-2012-6119 is a low-severity vulnerability in n/a, published on 2 Apr 2013. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Candlepin before 0.7.24, as used in Red Hat Subscription Asset Manager before 1.2.1, does not properly check manifest signatures, which allows local users to modify manifests.

Weakness: CWE-264

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

It affects 2 products.


Products: Candlepinproject Candlepin, Redhat Subscription Asset Manager.

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

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

## Is CVE-2012-6119 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-1832](https://insights.sbomify.com/CVE-2023-1832/): Improper authorization check in the server component (medium 6.8)
- [CVE-2015-5187](https://insights.sbomify.com/CVE-2015-5187/): Information disclosure in n/a (medium 6.5)
- [CVE-2021-4142](https://insights.sbomify.com/CVE-2021-4142/): Auth bypass in candlepin (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2012-6119 is a low-severity vulnerability in n/a, published on 2 Apr 2013. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-6119 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-6119/ (Markdown: https://insights.sbomify.com/CVE-2012-6119/index.md)
```

## Sources

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

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