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.
{ "binaries": [ { "binary_name": "libzypp", "binary_version": "15.3.0-1build1" }, { "binary_name": "libzypp-bin", "binary_version": "15.3.0-1build1" }, { "binary_name": "libzypp-common", "binary_version": "15.3.0-1build1" }, { "binary_name": "libzypp-config", "binary_version": "15.3.0-1build1" }, { "binary_name": "libzypp-dev", "binary_version": "15.3.0-1build1" } ] }