Vulnerabilities · 2017 · Rpm
CVE-2017-7501
Rpm vulnerability
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.
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/404ef011c300207cdb1e531670384564aae04bdc · Patch
- lists.apache.org/thread.html/r58af02e294bd07f487e2c64ffc0a29b837db5600e33b6e698b9d696b%40%
- lists.apache.org/thread.html/rf4c02775860db415b4955778a131c2795223f61cb8c6a450893651e4%40%
- security.gentoo.org/glsa/201811-22
- nvd.nist.gov/vuln/detail/CVE-2017-7501
- cve.org/CVERecord?id=CVE-2017-7501
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.