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.
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Rpm | Rpm | 4.13.0.0 (including) | 4.13.0.2 (excluding) |
Rpm | Rpm | 4.14.0.0-rc1 (including) | 4.14.0.0-rc1 (including) |
Rpm | Rpm | 4.14.0.0-rc2 (including) | 4.14.0.0-rc2 (including) |