CVE-2017-9269 | lack of keypinning in libzypp could lead to repository switching

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.

Published: 2018-03-01 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2017-9269 is rated Moderate Risk (55.7/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.64%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2017-9269

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-01 0.45% 0.64% +0.19%
2 2025-09-21 0.45% 0.45% +0.00%
3 2025-09-15 — 0.45% —

Full EPSS history (8 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2017-9269

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.7 3.0 HIGH
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 2.2 5.5 [email protected]
9.8 3.0 CRITICAL
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2017-9269

OS Trackers for CVE-2017-9269

vendor priority summary link
debian not yet assigned CVE-2017-9269 not yet assigned priority: Debian including 1 source packages (libzypp), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2017-9269
suse medium CVE-2017-9269 severity moderate: SUSE including 387 source package names (0.9.1:libzypp-16.17.20-2.33.2, 0.9.1:zypper-1.13.45-21.21.2, …), 507 product×package rows across 96 product lines (Container caasp/v4/default-http-backend, Container caasp/v4/dnsmasq-nanny, … (96 product lines)): Fixed 342, Known Affected 157, Known Not Affected 8. https://www.suse.com/security/cve/CVE-2017-9269/
ubuntu medium CVE-2017-9269 medium priority: Ubuntu including 1 source packages (libzypp), 21 status rows across 21 suites (artful, bionic, cosmic, disco, eoan, focal, groovy, hirsute, impish, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial, zesty): not-affected 14, DNE 3, ignored 2, needed 1, released 1. https://ubuntu.com/security/CVE-2017-9269

Affected software / configurations for CVE-2017-9269

Vendor Product Version Raw CPE
opensuse libzypp — cpe:2.3:a:opensuse:libzypp:-:*:*:*:*:*:*:*

References for CVE-2017-9269

cvelogic Threat Intelligence