{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-7685 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2018-7685 is a high-severity vulnerability in SUSE libzypp, published on 31 Aug 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2018-7685 and fix it if it is affected.\n\nWhat it is: CVE-2018-7685 is a high-severity vulnerability in SUSE libzypp, published on 31 Aug 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2018-7685 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-2018-7685/ (Markdown: https://insights.sbomify.com/CVE-2018-7685/index.md)","id":"CVE-2018-7685","markdown":"https://insights.sbomify.com/CVE-2018-7685/index.md","name":"CVE-2018-7685","record":{"aliases":["DEBIAN-CVE-2018-7685","GHSA-mrf9-ghhp-cjff","UBUNTU-CVE-2018-7685"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SUSE package manager library","requires_auth":"none","summary":"Attackers can bypass RPM integrity checks by exploiting decoupled download and installation steps, allowing malicious packages to be installed without warnings.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"microfocus","cpe":[{"product":"libzypp","vendor":"opensuse"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"},{"id":"CWE-358","name":"Improperly Implemented Security Check for Standard"}],"description":"The decoupled download and installation steps in libzypp before 17.5.0 could lead to a corrupted RPM being left in the cache, where a later call would not display the corrupted RPM warning and allow installation, a problem caused by malicious warnings only displayed during download.","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":"libzypp does not reevaluate malicious rpms once downloaded","id":"CVE-2018-7685","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2018"},"n_packages":0,"n_references":3,"next":{"headline":"Information disclosure in eDirectory (ZDI)","id":"CVE-2018-7686"},"packages":[],"prev":{"headline":"Information disclosure in Solutions Business Manager 11.4","id":"CVE-2018-7683"},"products":["libzypp"],"published":"2018-08-31","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.7,"headline":"lack of keypinning in libzypp could lead to repository switching","id":"CVE-2017-9269","kev_date_added":null,"published":"2018-03-01"},{"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 RPM integrity checks by exploiting decoupled download and installation steps, allowing malicious packages to be installed without warnings.","url":"https://insights.sbomify.com/CVE-2018-7685/"}