Ansible TowerApplication · Redhat
CVE-2020-14327
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA Server-side request forgery (SSRF) flaw was found in Ansible Tower in versions before 3.6.5 and before 3.7.2. Functionality on the Tower server is abused by supplying a URL that could lead to the server processing it. This flaw leads to the connection to internal services or the exposure of additional internal services by abusing the test feature of lookup credentials to forge HTTP/HTTPS requests from the server and retrieving the results of the response.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceAn SSRF vulnerability in Ansible Tower's lookup credentials test feature allows attackers to supply malicious URLs that cause the server to make HTTP/HTTPS requests to internal services, potentially exposing sensitive internal infrastructure and data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Ansible TowerApplication
< 3.6.5>= 3.7.0, < 3.7.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Ansible Tower installationCheck the installed Ansible Tower version via the API endpoint /api/v2/ping/ or by running 'awx-manage --version' on the Tower serverAffected if Unable to retrieve version information means Tower may not be installed as expected
-
Compare version to affected rangesReview the version number returned from the ping API or awx-manage command against the vulnerable ranges: < 3.6.5 or >= 3.7.0 and < 3.7.2Affected if The installed version falls within < 3.6.5 or >= 3.7.0 but < 3.7.2
-
Verify lookup credentials test feature accessCheck if the /api/v2/credentials/ endpoint's test/lookup functionality is exposed and accessible to users. This typically requires authentication but can be triggered via POST requests to /api/v2/credentials/N//test/Affected if The lookup credentials test endpoint responds and allows arbitrary URL submission, indicating the vulnerable feature is present
-
Check for signs of exploitationReview Tower audit logs and API access logs for patterns indicating the /test/ endpoint was called with internal URLs (e.g., http://localhost, http://127.0.0.1, http://169.254.169.254, or other internal IP ranges)Affected if Historical logs show unexpected internal URL requests from the Tower server to the lookup credentials test endpoint
A user is affected if their Ansible Tower version is less than 3.6.5 or falls between 3.7.0 and 3.7.2 inclusive, and the lookup credentials test feature is accessible to potentially malicious actors.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data3.6.53.7.2
Upgrade Ansible Tower to version 3.6.5, 3.7.2, or later to patch the SSRF vulnerability in the lookup credentials test feature.
Fix this in Ansible Tower
Scoped from the published advisory
- Consultation3.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14327 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-14327 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data