CVE-2017-7500

What it is

It was found that rpm did not properly handle RPM installations when a destination path was a symbolic link to a directory, possibly changing ownership and permissions of an arbitrary directory, and RPM files being placed in an arbitrary destination. An attacker, with write access to a directory in which a subdirectory will be installed, could redirect that directory to an arbitrary location and gain root privilege.

At a glance

Exploitability

Can be exploited locally on the machine with a low-privilege account, but needs a user to act. High risk of data exposure, data tampering, service disruption.

Exploit odds

0.4% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2018-08-13 17:29 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-17 01:24 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 0.4% in the next 30 days (EPSS).
• Severity: 7.3 HIGH (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2018-08-13 17:29 UTC

Last modified

2026-06-17 01:24 UTC

Exploit probability

0.4% · EPSS, next 30 days

Weakness

CWE-59

Record status

Modified

Affected

• Rpm < 4.13.0.2
• Rpm 4.14.0.0

Attack profile CVSS 3.0 · 7.3

Attack vector

Local

Complexity

Low

Privileges needed

Low

User interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2017-7500.md and follow it. Check whether this project is affected by CVE-2017-7500. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge