{"answers":{"affected":"7 open source packages ship an affected version, including ansible. It affects 4 products.","exploited":"There is no known exploitation of CVE-2018-10874 in the wild and no public exploit code.","fix":"Upgrade ansible to a fixed version for your release line: 2.4.6.0, 2.5.6 or 2.6.1.","what":"CVE-2018-10874 is a high-severity code injection vulnerability in Redhat Openstack, published on 2 Jul 2018. 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-2018-10874 and fix it if it is affected.\n\nWhat it is: CVE-2018-10874 is a high-severity code injection vulnerability in Redhat Openstack, published on 2 Jul 2018. 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-2018-10874 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ansible (PyPI): affected all versions; fixed in 2.4.6.0, 2.5.6, 2.6.1\n- ansible (PyPI): affected all versions; fixed in 2.4.6.0\n- ansible (PyPI): affected all versions; fixed in 2.4.6.0\n- ansible (PyPI): affected from 2.5; fixed in 2.5.6\n- ansible (PyPI): affected from 2.5; fixed in 2.5.6\n- ansible (PyPI): affected from 2.6; fixed in 2.6.1\n- ansible (PyPI): affected from 2.6; fixed in 2.6.1\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-10874/ (Markdown: https://insights.sbomify.com/CVE-2018-10874/index.md)","id":"CVE-2018-10874","markdown":"https://insights.sbomify.com/CVE-2018-10874/index.md","name":"CVE-2018-10874","record":{"aliases":["DEBIAN-CVE-2018-10874","GHSA-3xvg-x47j-x75w","PYSEC-2018-81","UBUNTU-CVE-2018-10874"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ansible automation tool","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary code by placing malicious inventory variables in the current working directory during ad-hoc command execution.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"ansible_engine","vendor":"redhat"},{"product":"openstack","vendor":"redhat"},{"product":"virtualization","vendor":"redhat"},{"product":"virtualization_host","vendor":"redhat"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"},{"id":"CWE-426","name":"Untrusted Search Path"}],"description":"In ansible it was found that inventory variables are loaded from current working directory when running ad-hoc command which are under attacker's control, allowing to run arbitrary code as a result.","ecosystems":["PyPI"],"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":"Ansible Improper Input Validation vulnerability","id":"CVE-2018-10874","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"redhat:openstack","products":["redhat:openstack","redhat:virtualization","redhat:virtualization_host"],"type":"code_injection","year":"2018"},"n_packages":7,"n_references":11,"next":{"headline":"Ansible Arbitrary Code Execution","id":"CVE-2018-10875"},"packages":[{"ecosystem":"PyPI","fixed":["2.4.6.0","2.5.6","2.6.1"],"introduced":["0","2.5","2.6"],"last_affected":[],"package":"ansible","purl":"pkg:pypi/ansible","source":"PYSEC-2018-81"},{"ecosystem":"PyPI","fixed":["2.4.6.0"],"introduced":["0"],"last_affected":[],"package":"ansible","purl":null,"source":"GHSA-3xvg-x47j-x75w"},{"ecosystem":"PyPI","fixed":["2.4.6.0"],"introduced":["0"],"last_affected":[],"package":"ansible","purl":"pkg:pypi/ansible","source":"GHSA-3xvg-x47j-x75w"},{"ecosystem":"PyPI","fixed":["2.5.6"],"introduced":["2.5"],"last_affected":[],"package":"ansible","purl":null,"source":"GHSA-3xvg-x47j-x75w"},{"ecosystem":"PyPI","fixed":["2.5.6"],"introduced":["2.5"],"last_affected":[],"package":"ansible","purl":"pkg:pypi/ansible","source":"GHSA-3xvg-x47j-x75w"},{"ecosystem":"PyPI","fixed":["2.6.1"],"introduced":["2.6"],"last_affected":[],"package":"ansible","purl":null,"source":"GHSA-3xvg-x47j-x75w"},{"ecosystem":"PyPI","fixed":["2.6.1"],"introduced":["2.6"],"last_affected":[],"package":"ansible","purl":"pkg:pypi/ansible","source":"GHSA-3xvg-x47j-x75w"}],"prev":{"headline":"Memory corruption in spice:","id":"CVE-2018-10873"},"products":["ansible"],"published":"2018-07-02","related":[{"cvss_score":7.5,"headline":"Path Traversal in Ansible","id":"CVE-2020-1737","kev_date_added":null,"published":"2020-03-09"},{"cvss_score":7.4,"headline":"OS Command Injection in ansible","id":"CVE-2020-1734","kev_date_added":null,"published":"2020-03-03"},{"cvss_score":7.3,"headline":"Ansible leaks sensitive information to logs when told not to","id":"CVE-2019-14858","kev_date_added":null,"published":"2019-10-14"},{"cvss_score":5.2,"headline":"Path Traversal in Ansible","id":"CVE-2020-10691","kev_date_added":null,"published":"2020-04-30"},{"cvss_score":4.2,"headline":"Ansible Logs Passwords If PowerShell ScriptBlock is Enabled","id":"CVE-2018-16859","kev_date_added":null,"published":"2018-11-29"},{"cvss_score":2.2,"headline":"Improper Input Validation in ansible","id":"CVE-2016-8647","kev_date_added":null,"published":"2018-07-26"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":["[UNKNOWN]"]},"summary":"Attackers can execute arbitrary code by placing malicious inventory variables in the current working directory during ad-hoc command execution.","url":"https://insights.sbomify.com/CVE-2018-10874/"}