{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11075 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-11075 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-11075 is a high-severity command injection vulnerability in anchore-engine, published on 27 May 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-11075 and fix it if it is affected.\n\nWhat it is: CVE-2020-11075 is a high-severity command injection vulnerability in anchore-engine, published on 27 May 2020. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-11075 in the wild and no public exploit code.\n\nAffected product: anchore-engine. 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-2020-11075/ (Markdown: https://insights.sbomify.com/CVE-2020-11075/index.md)","id":"CVE-2020-11075","markdown":"https://insights.sbomify.com/CVE-2020-11075/index.md","name":"CVE-2020-11075","record":{"aliases":["GHSA-w4rm-w22x-h7m5"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["code_execution","data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Container security scanner","requires_auth":"low_privilege","summary":"An authenticated attacker can execute arbitrary commands in the Anchore Engine analyzer environment by submitting a malicious container image manifest.","user_interaction":"required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"engine","vendor":"anchore"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-114","name":"Process Control"}],"description":"In Anchore Engine version 0.7.0, a specially crafted container image manifest, fetched from a registry, can be used to trigger a shell escape flaw in the anchore engine analyzer service during an image analysis process. The image analysis operation can only be executed by an authenticated user via a valid API request to anchore engine, or if an already added image that anchore is monitoring has its manifest altered to exploit the same flaw. A successful attack can be used to execute commands that run in the analyzer environment, with the same permissions as the user that anchore engine is run as - including access to the credentials that Engine uses to access its own database which have read-write ability, as well as access to the running engien analyzer service environment. By default Anchore Engine is released and deployed as a container where the user is non-root, but if users run Engine directly or explicitly set the user to 'root' then that level of access may be gained in the execution environment where Engine runs. This issue is fixed in version 0.7.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Shell Escape in Anchore Engine","id":"CVE-2020-11075","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"HTTP Smuggling via Transfer-Encoding Header in Puma","id":"CVE-2020-11076"},"packages":[],"prev":{"headline":"Stored XSS in PrestaShop","id":"CVE-2020-11074"},"products":["anchore-engine"],"published":"2020-05-27","related":[],"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-04","vendors":["anchore"]},"summary":"An authenticated attacker can execute arbitrary commands in the Anchore Engine analyzer environment by submitting a malicious container image manifest.","url":"https://insights.sbomify.com/CVE-2020-11075/"}