{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-9269 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2017-9269 is a high-severity vulnerability in SUSE libzypp, published on 1 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-9269 and fix it if it is affected.\n\nWhat it is: CVE-2017-9269 is a high-severity vulnerability in SUSE libzypp, published on 1 Mar 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2017-9269 in the wild and no public exploit code.\n\nAffected product: SUSE libzypp. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2017-9269/ (Markdown: https://insights.sbomify.com/CVE-2017-9269/index.md)","id":"CVE-2017-9269","markdown":"https://insights.sbomify.com/CVE-2017-9269/index.md","name":"CVE-2017-9269","record":{"aliases":["DEBIAN-CVE-2017-9269","GHSA-fvp9-wx3h-666q","UBUNTU-CVE-2017-9269"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SUSE package manager library","requires_auth":"none","summary":"Attackers can bypass GPG key pinning in libzypp to force repository downgrades, enabling the installation of malicious unsigned packages.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microfocus","cpe":[{"product":"libzypp","vendor":"opensuse"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:L","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-757","name":"Selection of Less-Secure Algorithm During Negotiation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"lack of keypinning in libzypp could lead to repository switching","id":"CVE-2017-9269","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"post-auth arbitrary file write on cryptctl server","id":"CVE-2017-9270"},"packages":[],"prev":{"headline":"open-build-service retrigger / wipebinaries hitting the wrong project bypassing access permissions","id":"CVE-2017-9268"},"products":["libzypp"],"published":"2018-03-01","related":[{"cvss_score":8.8,"headline":"Handcrafted repo metadata may cause arbitrary local files to be overwritten by libzypp","id":"CVE-2026-25707","kev_date_added":null,"published":"2026-06-29"},{"cvss_score":8.4,"headline":"libzypp path traversal via \"keyhint\" in repomd.xml","id":"CVE-2026-44941","kev_date_added":null,"published":"2026-07-02"},{"cvss_score":8.1,"headline":"libzypp accepts unsigned 3rd party repo without warning","id":"CVE-2017-7435","kev_date_added":null,"published":"2018-03-01"},{"cvss_score":8.1,"headline":"libzypp accepts unsigned packages even when configured to check signatures","id":"CVE-2017-7436","kev_date_added":null,"published":"2018-03-01"},{"cvss_score":7.8,"headline":"libzypp does not reevaluate malicious rpms once downloaded","id":"CVE-2018-7685","kev_date_added":null,"published":"2018-08-31"},{"cvss_score":4,"headline":"libzypp stores cookies world readable","id":"CVE-2019-18900","kev_date_added":null,"published":"2020-01-24"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["SUSE"]},"summary":"Attackers can bypass GPG key pinning in libzypp to force repository downgrades, enabling the installation of malicious unsigned packages.","url":"https://insights.sbomify.com/CVE-2017-9269/"}