{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2017-18641 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2017-18641 is a high-severity vulnerability in n/a, published on 10 Feb 2020. 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-18641 and fix it if it is affected.\n\nWhat it is: CVE-2017-18641 is a high-severity vulnerability in n/a, published on 10 Feb 2020. 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-18641 in the wild and no public exploit code.\n\nAffected product: n/a. 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-18641/ (Markdown: https://insights.sbomify.com/CVE-2017-18641/index.md)","id":"CVE-2017-18641","markdown":"https://insights.sbomify.com/CVE-2017-18641/index.md","name":"CVE-2017-18641","record":{"aliases":["DEBIAN-CVE-2017-18641","GHSA-rv6g-hrqv-7f3p","UBUNTU-CVE-2017-18641"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"LXC container templates","requires_auth":"none","summary":"Attackers can inject malicious code into LXC containers by intercepting unverified HTTP downloads during template bootstrapping.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lxc","vendor":"linuxcontainers"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"In LXC 2.0, many template scripts download code over cleartext HTTP, and omit a digital-signature check, before running it to bootstrap containers.","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":"Supply chain in n/a","id":"CVE-2017-18641","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"supply_chain","year":"2017"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2017-18642"},"packages":[],"prev":{"headline":"SnakeYAML Entity Expansion during load operation","id":"CVE-2017-18640"},"products":["n/a"],"published":"2020-02-10","related":[{"cvss_score":9.1,"headline":"Path traversal in LXC before 1.0.9 and 2.x before 2.0.6","id":"CVE-2016-8649","kev_date_added":null,"published":"2017-05-01"},{"cvss_score":8.6,"headline":"Privilege escalation in n/a","id":"CVE-2016-10124","kev_date_added":null,"published":"2017-01-09"},{"cvss_score":7.2,"headline":"Privilege escalation in n/a","id":"CVE-2013-6441","kev_date_added":null,"published":"2014-02-14"},{"cvss_score":4.9,"headline":"Path traversal in n/a","id":"CVE-2015-1331","kev_date_added":null,"published":"2015-08-12"},{"cvss_score":4.6,"headline":"Privilege escalation in n/a","id":"CVE-2015-1334","kev_date_added":null,"published":"2015-08-12"},{"cvss_score":4.3,"headline":"lxc lxc-user-nic insufficient ownership validation allows cross-tenant OVS port deletion","id":"CVE-2026-39402","kev_date_added":null,"published":"2026-05-05"}],"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-08-05","vendors":["n/a"]},"summary":"Attackers can inject malicious code into LXC containers by intercepting unverified HTTP downloads during template bootstrapping.","url":"https://insights.sbomify.com/CVE-2017-18641/"}