CVE-2017-9269

lack of keypinning in libzypp could lead to repository switching

Description

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.

Categories

7.7
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.33%
Vendor Advisory opensuse.org
Affected: SUSE libzypp
Published at:
Updated at:

References

Frequently Asked Questions

What is the severity of CVE-2017-9269?
CVE-2017-9269 has been scored as a high severity vulnerability.
How to fix CVE-2017-9269?
To fix CVE-2017-9269, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-9269 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-9269 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-9269?
CVE-2017-9269 affects SUSE libzypp.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.