{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-13139 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2019-13139 is a high-severity command injection vulnerability in n/a, published on 22 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-13139 and fix it if it is affected.\n\nWhat it is: CVE-2019-13139 is a high-severity command injection vulnerability in n/a, published on 22 Aug 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-13139 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-2019-13139/ (Markdown: https://insights.sbomify.com/CVE-2019-13139/index.md)","id":"CVE-2019-13139","markdown":"https://insights.sbomify.com/CVE-2019-13139/index.md","name":"CVE-2019-13139","record":{"aliases":["DEBIAN-CVE-2019-13139","GHSA-33j8-c2xf-8225","RHBA-2019:3092"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Docker build tool","requires_auth":"none","summary":"Attackers can execute arbitrary commands by manipulating build paths in Docker, leading to code execution on the host system.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"docker","vendor":"docker"}],"cvss":{"score":8.4,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"In Docker before 18.09.4, an attacker who is capable of supplying or manipulating the build path for the \"docker build\" command would be able to gain command execution. An issue exists in the way \"docker build\" processes remote git URLs, and results in command injection into the underlying \"git clone\" command, leading to code execution in the context of the user executing the \"docker build\" command. This occurs because git ref can be misinterpreted as a flag.","ecosystems":["Red Hat:rhel_extras_other:7"],"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":"Command injection in n/a","id":"CVE-2019-13139","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2019"},"n_packages":9,"n_references":7,"next":{"headline":"Information disclosure in n/a","id":"CVE-2019-13140"},"packages":[{"ecosystem":"Red Hat:rhel_extras_other:7","fixed":["2:1.13.1-104.git4ef4b30.el7"],"introduced":["0"],"last_affected":[],"package":"docker","purl":"pkg:rpm/redhat/docker","source":"RHBA-2019:3092"},{"ecosystem":"Red Hat:rhel_extras_other:7","fixed":["2:1.13.1-104.git4ef4b30.el7"],"introduced":["0"],"last_affected":[],"package":"docker-client","purl":"pkg:rpm/redhat/docker-client","source":"RHBA-2019:3092"},{"ecosystem":"Red Hat:rhel_extras_other:7","fixed":["2:1.13.1-104.git4ef4b30.el7"],"introduced":["0"],"last_affected":[],"package":"docker-common","purl":"pkg:rpm/redhat/docker-common","source":"RHBA-2019:3092"},{"ecosystem":"Red Hat:rhel_extras_other:7","fixed":["2:1.13.1-104.git4ef4b30.el7"],"introduced":["0"],"last_affected":[],"package":"docker-debuginfo","purl":"pkg:rpm/redhat/docker-debuginfo","source":"RHBA-2019:3092"},{"ecosystem":"Red Hat:rhel_extras_other:7","fixed":["2:1.13.1-104.git4ef4b30.el7"],"introduced":["0"],"last_affected":[],"package":"docker-logrotate","purl":"pkg:rpm/redhat/docker-logrotate","source":"RHBA-2019:3092"},{"ecosystem":"Red Hat:rhel_extras_other:7","fixed":["2:1.13.1-104.git4ef4b30.el7"],"introduced":["0"],"last_affected":[],"package":"docker-lvm-plugin","purl":"pkg:rpm/redhat/docker-lvm-plugin","source":"RHBA-2019:3092"},{"ecosystem":"Red Hat:rhel_extras_other:7","fixed":["2:1.13.1-104.git4ef4b30.el7"],"introduced":["0"],"last_affected":[],"package":"docker-novolume-plugin","purl":"pkg:rpm/redhat/docker-novolume-plugin","source":"RHBA-2019:3092"},{"ecosystem":"Red Hat:rhel_extras_other:7","fixed":["2:1.13.1-104.git4ef4b30.el7"],"introduced":["0"],"last_affected":[],"package":"docker-rhel-push-plugin","purl":"pkg:rpm/redhat/docker-rhel-push-plugin","source":"RHBA-2019:3092"},{"ecosystem":"Red Hat:rhel_extras_other:7","fixed":["2:1.13.1-104.git4ef4b30.el7"],"introduced":["0"],"last_affected":[],"package":"docker-v1.10-migrator","purl":"pkg:rpm/redhat/docker-v1.10-migrator","source":"RHBA-2019:3092"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-13137"},"products":["n/a"],"published":"2019-08-22","related":[{"cvss_score":10,"headline":"Arbitrary Code Execution","id":"CVE-2014-9357","kev_date_added":null,"published":"2014-12-16"},{"cvss_score":8.8,"headline":"Privilege escalation in Docker","id":"CVE-2020-14298","kev_date_added":null,"published":"2020-07-13"},{"cvss_score":8.8,"headline":"Privilege escalation in Docker","id":"CVE-2020-14300","kev_date_added":null,"published":"2020-07-13"},{"cvss_score":8.8,"headline":"Deserialization in n/a","id":"CVE-2018-15514","kev_date_added":null,"published":"2018-09-01"},{"cvss_score":8.6,"headline":"Path Traversal in Docker","id":"CVE-2014-9356","kev_date_added":null,"published":"2019-12-02"},{"cvss_score":8.1,"headline":"Other in n/a","id":"CVE-2014-5282","kev_date_added":null,"published":"2018-02-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHBA"},{"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":["n/a"]},"summary":"Attackers can execute arbitrary commands by manipulating build paths in Docker, leading to code execution on the host system.","url":"https://insights.sbomify.com/CVE-2019-13139/"}