CVE-2017-7501: It was found that versions of rpm before 4.13.0.2 use temporary files with predictable names when installing an RPM.
Noroxi assessment
Priority: Monitor (action score 31/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: 0.39% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: rpm (SUSE:Linux Enterprise Desktop 12 SP3) 4.11.2-16.16.1; rpm-python (SUSE:Linux Enterprise Desktop 12 SP3) 4.11.2-16.16.1; python3-rpm (SUSE:Linux Enterprise Server 12 SP3) 4.11.2-16.16.1.
Low priority for now. Upgrade to rpm (SUSE:Linux Enterprise Desktop 12 SP3) 4.11.2-16.16.1; rpm-python (SUSE:Linux Enterprise Desktop 12 SP3) 4.11.2-16.16.1; python3-rpm (SUSE:Linux Enterprise Server 12 SP3) 4.11.2-16.16.1 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
It was found that versions of rpm before 4.13.0.2 use temporary files with predictable names when installing an RPM. An attacker with ability to write in a directory where files will be installed could create symbolic links to an arbitrary location and modify content, and possibly permissions to arbitrary files, which could be used for denial of service or possibly privilege escalation.
- Published
- Nov 22, 2017
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 33th percentile
- CWE
- CWE-59
Report tools
Action score
31
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
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.
Is your version affected? Check itNoroxi 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 |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (redhat). Independent of NVD's CPE analysis and usually ahead of it.
Red Hat, Inc. rpm
- before 4.13.0.2affected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- rpm rpmbefore 4.13.0.3
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 | from 0 | — |
| SUSE:Linux Enterprise Desktop 12 SP3 | rpm | before 4.11.2-16.16.1 | 4.11.2-16.16.1 |
| SUSE:Linux Enterprise Desktop 12 SP3 | rpm-python | before 4.11.2-16.16.1 | 4.11.2-16.16.1 |
| SUSE:Linux Enterprise Server 12 SP3 | python3-rpm | before 4.11.2-16.16.1 | 4.11.2-16.16.1 |
| SUSE:OpenStack Cloud 7 | python3-rpm | before 4.11.2-16.21.1 | 4.11.2-16.21.1 |
| SUSE:OpenStack Cloud 7 | rpm | before 4.11.2-16.21.1 | 4.11.2-16.21.1 |
| SUSE:OpenStack Cloud 7 | rpm-python | before 4.11.2-16.21.1 | 4.11.2-16.21.1 |
Same product
rpm: all recordsOther highest-scoring records for the same primary product.
- CVE-2014-8118Integer overflow in RPM 4.12 and earlier allows remote attackers to execute arbitrary code via a crafted CPIO header in the payload section…42Plan
- 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…39Monitor
- 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…32Monitor
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…28Monitor
- ← 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…18Monitor
- Later →CVE-2017-7500Aug 13, 2018 · It was found that rpm did not properly handle RPM installations when a destination path was a symbolic link to a directory, possibly…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 |
|---|---|---|
| suse:python3-rpm | 4.11.2-16.16.1 · SUSE:Linux Enterprise Server 12 SP3 | Package registry (OSV) |
| suse:rpm | 4.11.2-16.16.1 · SUSE:Linux Enterprise Desktop 12 SP3 | Package registry (OSV) |
| suse:rpm-python | 4.11.2-16.16.1 · SUSE:Linux Enterprise Desktop 12 SP3 | 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.
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-59 · Improper Link Resolution Before File Access ('Link Following')CVSS vector
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
Attack patterns (CAPEC)
ATT&CK techniques
- Obfuscated Files or Information: HTML SmugglingT1027.006
- Obfuscated Files or Information: Embedded PayloadsT1027.009
- Boot or Logon Autostart Execution:Shortcut ModificationT1547.009
- Hide Artifacts: Resource ForkingT1564.009
- Hijack Execution Flow: Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: Services File Permissions WeaknessT1574.010
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.