{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10709 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10709 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10709 is a high-severity authentication bypass vulnerability in Redhat Ansible Tower, published on 27 May 2021. 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-2020-10709 and fix it if it is affected.\n\nWhat it is: CVE-2020-10709 is a high-severity authentication bypass vulnerability in Redhat Ansible Tower, published on 27 May 2021. 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-2020-10709 in the wild and no public exploit code.\n\nAffected product: Redhat Ansible Tower. 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-10709/ (Markdown: https://insights.sbomify.com/CVE-2020-10709/index.md)","id":"CVE-2020-10709","markdown":"https://insights.sbomify.com/CVE-2020-10709/index.md","name":"CVE-2020-10709","record":{"aliases":["GHSA-g252-frw3-5wcr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ansible Tower","requires_auth":"low_privilege","summary":"Attackers can obtain non-expiring OAuth2 refresh tokens, allowing persistent unauthorized access to Ansible Tower.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"ansible_tower","vendor":"redhat"}],"cvss":{"score":7.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"A security flaw was found in Ansible Tower when requesting an OAuth2 token with an OAuth2 application. Ansible Tower uses the token to provide authentication. This flaw allows an attacker to obtain a refresh token that does not expire. The original token granted to the user still has access to Ansible Tower, which allows any user that can gain access to the token to be fully authenticated to Ansible Tower. This flaw affects Ansible Tower versions before 3.6.4 and Ansible Tower versions before 3.5.6.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in Tower","id":"CVE-2020-10709","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:ansible_tower","products":["redhat:ansible_tower"],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in foreman-installer","id":"CVE-2020-10710"},"packages":[],"prev":{"headline":"DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2020-10708"},"products":["Tower"],"published":"2021-05-27","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in ansible-tower","id":"CVE-2018-10884","kev_date_added":null,"published":"2018-08-22"},{"cvss_score":8.8,"headline":"Code injection in Ansible Tower","id":"CVE-2018-1104","kev_date_added":null,"published":"2018-05-02"},{"cvss_score":8.4,"headline":"Information disclosure in Tower","id":"CVE-2019-14890","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":8.4,"headline":"Code injection in Ansible Tower","id":"CVE-2017-12148","kev_date_added":null,"published":"2018-07-27"},{"cvss_score":8.2,"headline":"Misconfiguration in Tower","id":"CVE-2019-19340","kev_date_added":null,"published":"2019-12-19"},{"cvss_score":8,"headline":"Privilege escalation in Ansible Tower","id":"CVE-2016-7070","kev_date_added":null,"published":"2018-09-11"},{"cvss_score":7.3,"headline":"Misconfiguration in Tower","id":"CVE-2018-16879","kev_date_added":null,"published":"2019-01-03"}],"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":["n/a"]},"summary":"Attackers can obtain non-expiring OAuth2 refresh tokens, allowing persistent unauthorized access to Ansible Tower.","url":"https://insights.sbomify.com/CVE-2020-10709/"}