{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15167 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-15167 is a high-severity code injection vulnerability in johnkerl miller, published on 2 Sep 2020. 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-2020-15167 and fix it if it is affected.\n\nWhat it is: CVE-2020-15167 is a high-severity code injection vulnerability in johnkerl miller, published on 2 Sep 2020. 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-2020-15167 in the wild and no public exploit code.\n\nAffected product: johnkerl miller. 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-15167/ (Markdown: https://insights.sbomify.com/CVE-2020-15167/index.md)","id":"CVE-2020-15167","markdown":"https://insights.sbomify.com/CVE-2020-15167/index.md","name":"CVE-2020-15167","record":{"aliases":["DEBIAN-CVE-2020-15167","GHSA-mw2v-4q78-j2cw","UBUNTU-CVE-2020-15167","openSUSE-SU-2024:11048-1"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Miller CLI utility","requires_auth":"none","summary":"Attackers can execute arbitrary code by placing a malicious configuration file in the working directory of the Miller command-line utility.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"miller","vendor":"johnkerl"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"},{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"In Miller (command line utility) using the configuration file support introduced in version 5.9.0, it is possible for an attacker to cause Miller to run arbitrary code by placing a malicious `.mlrrc` file in the working directory. See linked GitHub Security Advisory for complete details. A fix is ready and will be released as Miller 5.9.1.","ecosystems":["openSUSE:Tumbleweed"],"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":"Arbitrary code execution via configuration file in Miller","id":"CVE-2020-15167","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2020"},"n_packages":1,"n_references":1,"next":{"headline":"File size limit bypass in node-fetch","id":"CVE-2020-15168"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["5.10.2-1.3"],"introduced":["0"],"last_affected":[],"package":"miller","purl":"pkg:rpm/opensuse/miller\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:11048-1"}],"prev":{"headline":"Denial of Service in ZeroMQ","id":"CVE-2020-15166"},"products":["miller"],"published":"2020-09-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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":["johnkerl"]},"summary":"Attackers can execute arbitrary code by placing a malicious configuration file in the working directory of the Miller command-line utility.","url":"https://insights.sbomify.com/CVE-2020-15167/"}