The decoupled download and installation steps in libzypp before 17.5.0 could lead to a corrupted RPM being left in the cache, where a later call would not display the corrupted RPM warning and allow installation, a problem caused by malicious warnings only displayed during download.
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HOpensuse Libzypp
APPOpensuse< 17.5.0
Related vulnerabilities
A relative path traversal bug problem when processing repository metadata in libzypp before 17.38.10 could be ...
In libzypp before 20170803 it was possible to add unsigned YUM repositories without warning to the user that c...
In libzypp before 20170803 it was possible to retrieve unsigned packages without a warning to the user which c...
In libzypp before August 2018 GPG keys attached to YUM repositories were not correctly pinned, allowing malici...
: Incorrect Default Permissions vulnerability in libzypp of SUSE CaaS Platform 3.0, SUSE Linux Enterprise Serv...