Integer overflow in RPM 4.12 and earlier allows remote attackers to execute arbitrary code via a crafted CPIO header in the payload section
Noroxi assessment
Priority: Plan (action score 42/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 7.5% (FIRST EPSS); higher than 94.4% of all records.
- No special conditions are required; it is repeatable.
- Fixed version: rpm (Debian:12) 4.11.3-1.1; rpm (Debian:6.0) 4.8.1-6+squeeze2; rpm (Debian:7) 4.10.0-5+deb7u2.
Add it to your regular patch cycle. Upgrade to rpm (Debian:12) 4.11.3-1.1; rpm (Debian:6.0) 4.8.1-6+squeeze2; rpm (Debian:7) 4.10.0-5+deb7u2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Integer overflow in RPM 4.12 and earlier allows remote attackers to execute arbitrary code via a crafted CPIO header in the payload section of an RPM file, which triggers a stack-based buffer overflow.
- Published
- Dec 16, 2014
- Updated
- Jun 16, 2026
- EPSS
- 7.5% · 94th percentile
- CWE
- CWE-189
Report tools
Action score
42
Plan
Add it to your regular patch cycle.
- CVSS
- 40 / 40 · 10.0 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 7.5%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| rpm | rpm | cpe:2.3:a:rpm:rpm |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- rpm rpmup to 4.12.0 inclusive
- rpm rpm1.2
- rpm rpm1.3
- rpm rpm1.3.1
- rpm rpm1.4
- rpm rpm1.4.1
- rpm rpm1.4.2
- rpm rpm1.4.2/a
- rpm rpm1.4.3
- rpm rpm1.4.4
- rpm rpm1.4.5
- rpm rpm1.4.6
- rpm rpm1.4.7
- rpm rpm2.0
- rpm rpm2.0.1
- rpm rpm2.0.10
- rpm rpm2.0.11
- rpm rpm2.0.2
- rpm rpm2.0.3
- rpm rpm2.0.4
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | rpm | before 4.11.3-1.1 | 4.11.3-1.1 |
| Debian:6.0 | rpm | before 4.8.1-6+squeeze2 | 4.8.1-6+squeeze2 |
| Debian:7 | rpm | before 4.10.0-5+deb7u2 | 4.10.0-5+deb7u2 |
| Red Hat:enterprise_linux:7::client | rpm | before 0:4.11.1-18.el7_0 | 0:4.11.1-18.el7_0 |
| Red Hat:enterprise_linux:7::client | rpm-apidocs | before 0:4.11.1-18.el7_0 | 0:4.11.1-18.el7_0 |
| Red Hat:enterprise_linux:7::client | rpm-build | before 0:4.11.1-18.el7_0 | 0:4.11.1-18.el7_0 |
| Red Hat:enterprise_linux:7::client | rpm-build-libs | before 0:4.11.1-18.el7_0 | 0:4.11.1-18.el7_0 |
| Red Hat:enterprise_linux:7::client | rpm-cron | before 0:4.11.1-18.el7_0 | 0:4.11.1-18.el7_0 |
| Red Hat:enterprise_linux:7::client | rpm-debuginfo | before 0:4.11.1-18.el7_0 | 0:4.11.1-18.el7_0 |
| Red Hat:enterprise_linux:7::client | rpm-devel | before 0:4.11.1-18.el7_0 | 0:4.11.1-18.el7_0 |
| Red Hat:enterprise_linux:7::client | rpm-libs | before 0:4.11.1-18.el7_0 | 0:4.11.1-18.el7_0 |
| Red Hat:enterprise_linux:7::client | rpm-python | before 0:4.11.1-18.el7_0 | 0:4.11.1-18.el7_0 |
| Red Hat:enterprise_linux:7::client | rpm-sign | before 0:4.11.1-18.el7_0 | 0:4.11.1-18.el7_0 |
Same product
rpm: all recordsOther highest-scoring records for the same primary product.
- CVE-2011-3378RPM 4.4.x through 4.9.x, probably before 4.9.1.2, allows remote attackers to cause a denial of service (memory corruption) and possibly exec39Monitor
- CVE-2013-6435Race condition in RPM 4.11.1 and earlier allows remote attackers to execute arbitrary code via a crafted RPM file whose installation extract32Monitor
- CVE-2017-7500It was found that rpm did not properly handle RPM installations when a destination path was a symbolic link to a directory, possibly changin31Monitor
Published before and after this one in the same product
- ← EarlierCVE-2012-0815Jun 4, 2012 · The headerVerifyInfo function in lib/header.c in RPM before 4.9.1.3 allows remote attackers to cause a denial of service (crash) and possibl28Monitor
- ← EarlierCVE-2012-6088Jan 18, 2013 · 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 "unpar18Monitor
- Later →CVE-2017-7501Nov 22, 2017 · It was found that versions of rpm before 4.13.0.2 use temporary files with predictable names when installing an RPM.31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:rpm | 4.11.3-1.1 · Debian:12 | Package registry (OSV) |
| red hat:rpm | 0:4.11.1-18.el7_0 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:rpm-apidocs | 0:4.11.1-18.el7_0 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:rpm-build | 0:4.11.1-18.el7_0 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:rpm-build-libs | 0:4.11.1-18.el7_0 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:rpm-cron | 0:4.11.1-18.el7_0 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:rpm-debuginfo | 0:4.11.1-18.el7_0 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:rpm-devel | 0:4.11.1-18.el7_0 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:rpm-libs | 0:4.11.1-18.el7_0 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:rpm-python | 0:4.11.1-18.el7_0 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
| red hat:rpm-sign | 0:4.11.1-18.el7_0 · Red Hat:enterprise_linux:7::client | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- C · data or configuration can be modified
- Availability
- C · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- C
- Availability impact
- C
Weakness class (CWE)
CWE-189 · Numeric ErrorsCVSS vector
AV:N/AC:L/Au:N/C:C/I:C/A:C
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.