{"answers":{"affected":"5 open source packages ship an affected version, including ansible. It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-10744 in the wild and no public exploit code.","fix":"Upgrade ansible to a fixed version for your release line: 2.9.12, 2.10.0rc1, 2.8.0a1 or 2.8.13.","what":"CVE-2020-10744 is a medium-severity vulnerability in Redhat Ansible Tower, published on 15 May 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-10744 and fix it if it is affected.\n\nWhat it is: CVE-2020-10744 is a medium-severity vulnerability in Redhat Ansible Tower, published on 15 May 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-10744 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ansible (PyPI): affected all versions; fixed in 2.9.12\n- ansible (PyPI): affected all versions; fixed in 2.9.12\n- ansible (PyPI): affected from 2.10.0a1; fixed in 2.10.0rc1\n- ansible (PyPI): affected from 2.10.0a1; fixed in 2.10.0rc1\n- ansible (PyPI): affected from 2.7.0; fixed in 2.8.0a1, 2.8.13, 2.9.10\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-10744/ (Markdown: https://insights.sbomify.com/CVE-2020-10744/index.md)","id":"CVE-2020-10744","markdown":"https://insights.sbomify.com/CVE-2020-10744/index.md","name":"CVE-2020-10744","record":{"aliases":["DEBIAN-CVE-2020-10744","GHSA-vp9j-rghq-8jhh","PYSEC-2020-208","UBUNTU-CVE-2020-10744"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Ansible automation tool","requires_auth":"low_privilege","summary":"Attackers can exploit a race condition in Ansible's temporary directory handling on systems with ACLs or FUSE to escalate privileges or execute code.","user_interaction":"required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"ansible","vendor":"redhat"},{"product":"ansible_tower","vendor":"redhat"}],"cvss":{"score":5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"},{"id":"CWE-377","name":"DEPRECATED: Insecure Temporary File"}],"description":"An incomplete fix was found for the fix of the flaw CVE-2020-1733 ansible: insecure temporary directory when running become_user from become directive. The provided fix is insufficient to prevent the race condition on systems using ACLs and FUSE filesystems. Ansible Engine 2.7.18, 2.8.12, and 2.9.9 as well as previous versions are affected and Ansible Tower 3.4.5, 3.5.6 and 3.6.4 as well as previous versions are affected.","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":"Exposure of Resource to Wrong Sphere and Insecure Temporary File in Ansible","id":"CVE-2020-10744","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":"redhat:ansible_tower","products":["redhat:ansible_tower"],"type":"race_condition","year":"2020"},"n_packages":5,"n_references":1,"next":{"headline":"Denial of service in Samba","id":"CVE-2020-10745"},"packages":[{"ecosystem":"PyPI","fixed":["2.9.12"],"introduced":["0"],"last_affected":[],"package":"ansible","purl":null,"source":"GHSA-vp9j-rghq-8jhh"},{"ecosystem":"PyPI","fixed":["2.9.12"],"introduced":["0"],"last_affected":[],"package":"ansible","purl":"pkg:pypi/ansible","source":"GHSA-vp9j-rghq-8jhh"},{"ecosystem":"PyPI","fixed":["2.10.0rc1"],"introduced":["2.10.0a1"],"last_affected":[],"package":"ansible","purl":null,"source":"GHSA-vp9j-rghq-8jhh"},{"ecosystem":"PyPI","fixed":["2.10.0rc1"],"introduced":["2.10.0a1"],"last_affected":[],"package":"ansible","purl":"pkg:pypi/ansible","source":"GHSA-vp9j-rghq-8jhh"},{"ecosystem":"PyPI","fixed":["2.8.0a1","2.8.13","2.9.10"],"introduced":["2.7.0","2.8.0","2.9.0"],"last_affected":[],"package":"ansible","purl":"pkg:pypi/ansible","source":"PYSEC-2020-208"}],"prev":{"headline":"Cross-site request forgery in Kibana","id":"CVE-2020-10743"},"products":["ansible"],"published":"2020-05-15","related":[{"cvss_score":9.8,"headline":"Ansible Remote Code Execution","id":"CVE-2014-4657","kev_date_added":null,"published":"2020-02-20"},{"cvss_score":9.8,"headline":"Ansible Arbitrary Code Execution","id":"CVE-2014-4966","kev_date_added":null,"published":"2020-02-18"},{"cvss_score":9.8,"headline":"Ansible Arbitrary Code Execution","id":"CVE-2014-4967","kev_date_added":null,"published":"2020-02-18"},{"cvss_score":9.8,"headline":"Ansible Insertion of Sensitive Information into Log File vulnerability","id":"CVE-2017-7550","kev_date_added":null,"published":"2017-11-21"},{"cvss_score":8.8,"headline":"Ansible Arbitrary Code Execution","id":"CVE-2014-3498","kev_date_added":null,"published":"2017-06-08"},{"cvss_score":8,"headline":"Ansible Arbitrary Code Execution","id":"CVE-2017-7466","kev_date_added":null,"published":"2018-06-22"},{"cvss_score":7.8,"headline":"Ansible Sandbox Escape via Symlink Attack","id":"CVE-2015-6240","kev_date_added":null,"published":"2017-06-07"}],"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-04","vendors":["Red Hat"]},"summary":"Attackers can exploit a race condition in Ansible's temporary directory handling on systems with ACLs or FUSE to escalate privileges or execute code.","url":"https://insights.sbomify.com/CVE-2020-10744/"}