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.
CPE | Name | Operator | Version |
---|---|---|---|
rpm | eq | 4.14.0.0 rc1 | |
rpm | eq | 4.14.0.0 rc2 | |
rpm | ge | 4.13.0.0 | |
rpm | lt | 4.13.0.2 |