Skip to content
Fencer Intel
medium 4.3

CVE-2012-6088 json

The rpmpkgRead function in lib/package.c in RPM 4.10.x before 4.10.2 does not return an error code in certain situations involving an "unpa…

published 2013-01-18 13 y ago modified 2026-06-16 4 mo ago also EUVD-2012-5959

cvss
4.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

The rpmpkgRead function in lib/package.c in RPM 4.10.x before 4.10.2 does not return an error code in certain situations involving an "unparseable signature," which allows remote attackers to bypass RPM signature checks via a crafted package.

Patch / fix

  • rpm Debian 14, Debian 13, Debian 12 4.10.1-2.1

debian advisories DEBIAN-CVE-2012-6088

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-6088 updated cvss 6.2

rpm: Signature checking function returned success on (possibly malicious ) rpm packages

  • Red Hat Enterprise Linux 6 rpm, rpm-cron, rpm-libs, rpm-build, rpm-python, rpm-apidocs Red Hat Enterprise Linux 7 rpm, rpm-cron, rpm-libs, rpm-sign, rpm-build, rpm-python, +3 more Red Hat Enterprise Linux 8 rpm, rpm-cron, rpm-libs, rpm-sign, rpm-build, python3-rpm, +8 more Red Hat Enterprise Linux 9 rpm, rpm-cron, rpm-libs, rpm-sign, rpm-build, python3-rpm, +9 more
    not affected: vulnerable code not present

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

2.25% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-255 Credentials Management Errors

References

Sources

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.