{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-10697 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-10697 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-10697 is a medium-severity missing authorization 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-10697 and fix it if it is affected.\n\nWhat it is: CVE-2020-10697 is a medium-severity missing authorization 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-10697 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-10697/ (Markdown: https://insights.sbomify.com/CVE-2020-10697/index.md)","id":"CVE-2020-10697","markdown":"https://insights.sbomify.com/CVE-2020-10697/index.md","name":"CVE-2020-10697","record":{"aliases":["GHSA-rhg6-3qw6-38pp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ansible Tower","requires_auth":"low_privilege","summary":"An attacker can pollute the memcached cache via a playbook, causing denial of service or potentially accessing sensitive data in Ansible Tower.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"ansible_tower","vendor":"redhat"}],"cvss":{"score":4.4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"A flaw was found in Ansible Tower when running Openshift. Tower runs a memcached, which is accessed via TCP. An attacker can take advantage of writing a playbook polluting this cache, causing a denial of service attack. This attack would not completely stop the service, but in the worst-case scenario, it can reduce the Tower performance, for which memcached is designed. Theoretically, more sophisticated attacks can be performed by manipulating and crafting the cache, as Tower relies on memcached as a place to pull out setting values. Confidential and sensitive data stored in memcached should not be pulled, as this information is encrypted. This flaw affects Ansible Tower versions before 3.6.4, Ansible Tower versions before 3.5.6 and Ansible Tower versions before 3.4.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":"Missing authorization in Tower","id":"CVE-2020-10697","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:ansible_tower","products":["redhat:ansible_tower"],"type":"missing_authorization","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in Tower","id":"CVE-2020-10698"},"packages":[],"prev":{"headline":"Path Traversal in Buildah","id":"CVE-2020-10696"},"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":"An attacker can pollute the memcached cache via a playbook, causing denial of service or potentially accessing sensitive data in Ansible Tower.","url":"https://insights.sbomify.com/CVE-2020-10697/"}