CVE-2018-10884
Description
Ansible Tower before versions 3.1.8 and 3.2.6 is vulnerable to cross-site request forgery (CSRF) in awx/api/authentication.py. An attacker could exploit this by tricking already authenticated users into visiting a malicious site and hijacking the authtoken cookie.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Ansible Tower before 3.1.8 and 3.2.6 is vulnerable to CSRF in awx/api/authentication.py, allowing an attacker to hijack the authtoken cookie by tricking authenticated users into visiting a malicious site.
Vulnerability
Ansible Tower versions before 3.1.8 and 3.2.6 are vulnerable to cross-site request forgery (CSRF) in the awx/api/authentication.py file. The vulnerability allows an attacker to execute unauthorized actions on behalf of an authenticated user without their knowledge. No special configuration is required for the code path to be reachable; the CSRF protection is missing in the authentication module. [1]
Exploitation
An attacker must trick an already authenticated Ansible Tower user into visiting a malicious website or clicking a crafted link while logged in. The attacker can then exploit the lack of CSRF protection to perform requests that hijack the user's authtoken cookie. The attack does not require any special network position beyond the ability to serve the malicious page to the targeted user. [1]
Impact
Successful exploitation allows the attacker to hijack the authtoken cookie of the authenticated user. This can lead to session hijacking, where the attacker can impersonate the victim and gain the same privileges, potentially leading to unauthorized access to sensitive data or administrative actions within Ansible Tower. The compromise is at the session level, impacting confidentiality, integrity, and availability. [1]
Mitigation
Ansible Tower versions 3.1.8 and 3.2.6 contain the fix for this vulnerability. Users should upgrade to at least these versions. The bug was publicly disclosed in July 2018 with a fix available in the same release cycle. No workarounds are documented in the available references; upgrading is the recommended mitigation. [1]
AI Insight generated on May 26, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2- Range: < 3.1.8, < 3.2.6
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
2- www.securityfocus.com/bid/105136mitrevdb-entryx_refsource_BID
- bugzilla.redhat.com/show_bug.cgimitrex_refsource_CONFIRM
News mentions
0No linked articles in our index yet.