CVE-2017-7436 json
libzypp accepts unsigned packages even when configured to check signatures
published 2018-03-01 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-16460
- cvss
- 8.1
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- SUSE libzypp 20170803
- libzypp Debian 14, Debian 13, Debian 12 17.3.1-1
debian advisories DEBIAN-CVE-2017-7436
- zypper SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 1.13.32-21.3.2
- libzypp SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 +1 more 16.15.6-2.8.1
- libzypp SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 +1 more 16.15.3-2.3.1
- yast2-pkg-bindings SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 3.2.4-2.3.1
- zypper SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +1 more 1.13.30-18.13.3
- libzypp SLES for SAP 12 SP2, SLES for Raspberry Pi 12 SP2, SLES 12 SP2 +2 more 16.15.2-27.21.1
- zypper SLES 12-LTSS 1.11.70-2.69.2
- libzypp SLES 12-LTSS 14.45.17-2.82.1
suse advisories SUSE-SU-2018:2688-1SUSE-SU-2018:2555-1SUSE-SU-2017:2344-1SUSE-SU-2017:2264-1SUSE-SU-2017:2040-1
- zypper openSUSE Tumbleweed 1.14.49-1.2
opensuse advisories openSUSE-SU-2024:11545-1
Exploit prediction
1.82% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Affected products
- SUSE libzypp
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
Sources
- CVE List CVE-2017-7436
- NVD CVE-2017-7436
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.