Skip to content
Fencer Intel
high 7.7

CVE-2017-9269 json

lack of keypinning in libzypp could lead to repository switching

published 2018-03-01 8 y ago modified 2026-06-17 4 mo ago also EUVD-2017-18205

cvss
7.7
version 3.0, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.2%
EPSS 2.2% chance of exploitation in 30 days, percentile 83%
public exploits
0
none known

Summary

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.

Patch / fix

  • SUSE libzypp 201808
  • libzypp Debian 14, Debian 13, Debian 12 17.3.1-1

debian advisories DEBIAN-CVE-2017-9269

  • zypper SLES 12 SP2-BCL, OpenStack Cloud 7, Enterprise Storage 4 +2 more 1.13.45-18.33.1
  • libzypp SLES 12 SP2-BCL, OpenStack Cloud 7, Enterprise Storage 4 +2 more 16.17.20-27.52.1
  • zypper SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 1.13.45-21.21.2
  • libzypp SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 +1 more 16.17.20-2.33.2
  • zypper SLE Module for Basesystem 15 1.14.10-3.7.1
  • libsolv SLE Module for Development Tools 15, SLE Module for Basesystem 15 0.6.35-3.5.2
  • libzypp SLE Module for Basesystem 15 17.6.4-3.10.1
  • libzypp SLES for SAP 12 SP3, SLES 12 SP3, SLED 12 SP3 +1 more 16.15.3-2.3.1

suse advisories SUSE-SU-2018:2716-2SUSE-SU-2018:2814-1SUSE-SU-2018:2716-1SUSE-SU-2018:2690-1SUSE-SU-2018:2688-1SUSE-SU-2018:2555-1

  • libzypp openSUSE Tumbleweed 17.28.4-1.2
  • zypper openSUSE Tumbleweed 1.14.49-1.2

opensuse advisories openSUSE-SU-2024:11019-1openSUSE-SU-2024:11545-1

Exploit prediction

2.25% chance of exploitation in the next 30 days, higher than 83% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.0 7.7 CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Affected products

  • SUSE libzypp

Classification

Weakness
  • CWE-757 Selection of Less-Secure Algorithm During Negotiation
  • CWE-20 Improper Input Validation

References

Sources

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.