dbcve.org
RpmApplication

CVE-2012-0060

MEDIUM · 6.8 CVSS v2.0 Published 2012-06-04
Fix available
A fix is available. Upgrade to after 4.9.1.2 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

RPM before 4.9.1.3 fails to properly validate region tags in package headers, allowing malformed headers to be processed by headerLoad, rpmReadSignature, or headerVerify functions. This can cause crashes (denial of service) and potentially enable arbitrary code execution via crafted package headers.

MitigationUpgrade RPM to version 4.9.1.3 or later which includes proper region tag validation. Also implement input validation for any RPM package imports into the system.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
RpmApplication
Affected:<= 4.9.1.2= 1.2= 1.3= 1.3.1= 1.4= 1.4.1= 1.4.2= 1.4.2\/a= 1.4.3= 1.4.4= 1.4.5= 1.4.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify RPM is installed
    Run 'rpm --version' to confirm the rpm package manager is present on the system
    Affected if If the command returns an error or 'not found', RPM is not installed and this CVE does not apply
  2. Determine installed RPM version
    Run 'rpm --version' and capture the version number from the output (format typically shows as 'RPM version X.Y.Z')
    Affected if The exact version shown is needed to compare against affected ranges
  3. Compare version against affected list
    Check if the installed version matches any of the following: versions 1.2, 1.3, 1.3.1, 1.4, 1.4.1, 1.4.2, 1.4.2/a, 1.4.3, 1.4.4, 1.4.5, 1.4.6, or any 4.9.1.2 or earlier
    Affected if If the installed version is one of these specific versions or falls within the <=4.9.1.2 range, the system is vulnerable to malformed header processing via headerLoad, rpmReadSignature, or headerVerify functions

The system is affected if RPM is installed and the version matches 1.2 through 1.4.6 or is 4.9.1.2 or earlier, as these versions lack proper region tag validation in package headers

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 4.9.1.2
Interim mitigation

Upgrade RPM to version 4.9.1.3 or later which includes proper region tag validation. Also implement input validation for any RPM package imports into the system.

Fix this in Rpm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2012-0060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2012-0060 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data