Vulnerabilities · 2017 · Rpm
CVE-2017-7500
Rpm vulnerability
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.
Affected products
Rpm. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Rpm runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- github.com/rpm-software-management/rpm/commit/c815822c8bdb138066ff58c624ae83e3a12ebfa9 · Third Party Advisory
- github.com/rpm-software-management/rpm/commit/f2d3be2a8741234faaa96f5fd05fdfdc75779a79 · Third Party Advisory
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2017-7500
- nvd.nist.gov/vuln/detail/CVE-2017-7500
- cve.org/CVERecord?id=CVE-2017-7500
More vulnerabilities in Rpm products
CVE-2024-1929CVE-2021-35939CVE-2021-35938CVE-2021-35937CVE-2021-20271CVE-2021-20266CVE-2021-3521CVE-2021-3445All 26
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.