Suse Libzypp vulnerabilities
4 known vulnerabilities affecting suse/libzypp.
Total CVEs
4
CISA KEV
0
Public exploits
0
Exploited in wild
0
Severity breakdown
CRITICAL1HIGH3
Vulnerabilities
Page 1 of 1
CVE-2018-7685HIGHCVSS 7.8≥ unspecified, < 17.5.02018-08-31
CVE-2018-7685 [HIGH] CWE-358 CVE-2018-7685: The decoupled download and installation steps in libzypp before 17.5.0 could lead to a corrupted RPM
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.
cvelistv5nvd
CVE-2017-9269CRITICALCVSS 9.8≥ unspecified, < 2018082018-03-01
CVE-2017-9269 [HIGH] CWE-757 CVE-2017-9269: In libzypp before August 2018 GPG keys attached to YUM repositories were not correctly pinned, allow
In libzypp before August 2018 GPG keys attached to YUM repositories were not correctly pinned, allowing malicious repository mirrors to silently downgrade to unsigned repositories with potential malicious content.
cvelistv5nvd
CVE-2017-7436HIGHCVSS 8.1≥ unspecified, < 201708032018-03-01
CVE-2017-7436 [HIGH] CWE-20 CVE-2017-7436: In libzypp before 20170803 it was possible to retrieve unsigned packages without a warning to the us
In libzypp before 20170803 it was possible to retrieve unsigned packages without a warning to the user which could lead to man in the middle or malicious servers to inject malicious RPM packages into a users system.
cvelistv5nvd
CVE-2017-7435HIGHCVSS 8.1≥ unspecified, < 201708032018-03-01
CVE-2017-7435 [HIGH] CWE-20 CVE-2017-7435: In libzypp before 20170803 it was possible to add unsigned YUM repositories without warning to the u
In libzypp before 20170803 it was possible to add unsigned YUM repositories without warning to the user that could lead to man in the middle or malicious servers to inject malicious RPM packages into a users system.
cvelistv5nvd