CONTENTUM.COMA specialist. A plan. A result.

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

More vulnerabilities in Rpm products

Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.