Persistent authentication via ignored refresh-token expiration
Published May 27, 2021 · Updated Aug 4, 2024
Insufficient session expiration in Red Hat Ansible Tower before 3.5.6 and 3.6.0 through 3.6.3 allows remote authenticated users to retain access. The OAuth2 token endpoint accepts refresh tokens after REFRESH_TOKEN_EXPIRE_SECONDS has elapsed and issues new access and refresh tokens. Exploitation requires a previously issued refresh token and preserves that token's authorized Tower access without granting broader privileges.
Summary
What happened
Insufficient session expiration in Red Hat Ansible Tower before 3.5.6 and 3.6.0 through 3.6.3 allows remote authenticated users to retain access. The OAuth2 token endpoint accepts refresh tokens after REFRESH_TOKEN_EXPIRE_SECONDS has elapsed and issues new access and refresh tokens. Exploitation requires a previously issued refresh token and preserves that token's authorized Tower access without granting broader privileges.
The record
- CVE
- CVE-2020-10709
- Published
- May 27, 2021
- Updated
- Aug 4, 2024
- Vendor
- Red Hat
- Product
- Red Hat Ansible Tower
- Classifications
- CWE-287, CWE-613, T1528
- Attack vector
- network
- 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
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.
Weakness, pattern, technique
Public exploit references
- AWX expired refresh-token reproductionfunctional · demonstrated
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