CVE-2020-10709

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.

Category

7.1
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.09%
Vendor Advisory redhat.com
Affected: n/a Tower
Published at:
Updated at:

References

Link Tags
https://bugzilla.redhat.com/show_bug.cgi?id=1824033 issue tracking vendor advisory

Frequently Asked Questions

What is the severity of CVE-2020-10709?
CVE-2020-10709 has been scored as a high severity vulnerability.
How to fix CVE-2020-10709?
To fix CVE-2020-10709, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-10709 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-10709 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2020-10709?
CVE-2020-10709 affects n/a Tower.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.