Service degradation via writable TCP memcached cache
Published May 27, 2021 · Updated Aug 4, 2024
Missing authorization in Red Hat Ansible Tower on OpenShift before 3.4.6, 3.5.6, or 3.6.4 allows local users to degrade performance. Tower exposes memcached over TCP and permits playbook-driven writes that can pollute cache entries later consumed as settings. Low-privileged playbook access is required, and the resulting slowdown does not completely stop the service; sensitive cached values remain encrypted.
Summary
What happened
Missing authorization in Red Hat Ansible Tower on OpenShift before 3.4.6, 3.5.6, or 3.6.4 allows local users to degrade performance. Tower exposes memcached over TCP and permits playbook-driven writes that can pollute cache entries later consumed as settings. Low-privileged playbook access is required, and the resulting slowdown does not completely stop the service; sensitive cached values remain encrypted.
The record
- CVE
- CVE-2020-10697
- Published
- May 27, 2021
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- Red Hat Ansible Tower
- Classifications
- CWE-862, T1499
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=ansible_tower 3.6.4, ansible_tower 3.5.6, ansible_tower 3.4.6
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo