CVE-2012-6119 json
Candlepin before 0.7.24, as used in Red Hat Subscription Asset Manager before 1.2.1, does not properly check manifest signatures, which all…
published 2013-04-02 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5986
- cvss
- 2.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 36%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2012-6119 updated cvss 4.0
Candlepin: Re-enable manifest signature checking
-
Red Hat Subscription Asset Manager for RHEL 6 Server candlepin 0.7.24-1.el6_3, katello 1.2.1.1-1h.el6_4, rubygem-rdoc 3.8-6.el6cf, rubygem-json 1.7.3-2.el6_3, rubygem-rack 1.3.0-4.el6cf, thumbslug 0.0.28.1-1.el6_4, +14 morefixed: vendor fix RHSA-2013:0686
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.42% chance of exploitation in the next 30 days, higher than 36% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.1 | AV:L/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-264 Permissions, Privileges, and Access Controls
References
- github.com /candlepin/candlepin/commit/f4d93230e58b969c506b4c9778e04482a059b08c
-
rhn.redhat.com
/errata/RHSA-2013-0686.html
vendor-advisory
-
secunia.com
/advisories/52774
third-party-advisory, vendor-advisory
-
osvdb.org
/91719
vdb-entry
- bugzilla.redhat.com /show_bug.cgi?id=908613
- github.com /candlepin/candlepin/blob/master/candlepin.spec
Sources
- CVE List CVE-2012-6119
- NVD CVE-2012-6119
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.