Ansible TowerApplication · Redhat
CVE-2019-19340
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 flaw was found in Ansible Tower, versions 3.6.x before 3.6.2 and 3.5.x before 3.5.3, where enabling RabbitMQ manager by setting it with '-e rabbitmq_enable_manager=true' exposes the RabbitMQ management interface publicly, as expected. If the default admin user is still active, an attacker could guess the password and gain access to the system.
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 confidenceIn Ansible Tower versions 3.5.x before 3.5.3 and 3.6.x before 3.6.2, enabling the RabbitMQ manager via the '-e rabbitmq_enable_manager=true' flag exposes the RabbitMQ management interface publicly on the network. When the default admin user account remains active with its default or weak password, unauthenticated remote attackers can perform credential guessing attacks to gain unauthorized access to the system.
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.5.0, < 3.5.3>= 3.6.0, < 3.6.2
Enterprise LinuxOperating system
= 7.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:L
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.
-
Check Ansible Tower versionRun 'ansible-tower-cli status' or check /etc/ansible-tower/tower.conf for the installed version number, or query the API endpoint /api/v2/ping/Affected if The version is >= 3.5.0 and < 3.5.3, OR >= 3.6.0 and < 3.6.2
-
Verify if RabbitMQ manager was enabledSearch Tower job extra variables, inventory files, or configuration for the string 'rabbitmq_enable_manager=true' to determine if this flag was passed during setupAffected if The flag '-e rabbitmq_enable_manager=true' was used to enable the feature
-
Confirm RabbitMQ management interface network exposureReview firewall rules, security groups, or network ACLs to determine if TCP port 15672 (RabbitMQ management) is accessible from untrusted networks or the public internetAffected if The RabbitMQ management interface (port 15672) is exposed to public or untrusted networks without IP restrictions
-
Check default admin account statusQuery the RabbitMQ management interface or check /var/lib/rabbitmq/ for active users, and verify whether the default 'admin' account with default or weak credentials is still enabledAffected if The default admin user account remains active with its default password or a weak password
You are affected if your Ansible Tower version falls within the vulnerable range, the RabbitMQ manager was enabled with that flag, the management interface is network-accessible, and the default admin account is still active with default or weak credentials.
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.5.33.6.2
Disable the RabbitMQ manager if not required, or ensure the default admin user is disabled/changed to a strong password, and implement network-level access controls to restrict the management interface to authorized networks or VPN access only.
Fix this in Ansible Tower
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19340 — 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-2019-19340 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