CVE-2018-16879
First published: Thu Jan 03 2019(Updated: )
Ansible Tower before version 3.3.3 does not set a secure channel as it is using the default insecure configuration channel settings for messaging celery workers from RabbitMQ. This could lead in data leak of sensitive information such as passwords as well as denial of service attacks by deleting projects or inventory files.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Redhat Ansible Tower | <3.3.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2018-16879?
CVE-2018-16879 is a vulnerability that allows data leak and denial of service attacks in Ansible Tower versions prior to 3.3.3.
How severe is CVE-2018-16879?
CVE-2018-16879 has a severity rating of 9.8, which is considered critical.
What software is affected by CVE-2018-16879?
Ansible Tower versions up to and excluding 3.3.3 are affected by CVE-2018-16879.
How can CVE-2018-16879 be exploited?
CVE-2018-16879 can be exploited by an attacker to leak sensitive information and perform denial of service attacks by manipulating the insecure configuration channel settings for messaging celery workers from RabbitMQ.
How can I fix CVE-2018-16879?
To fix CVE-2018-16879, upgrade your Ansible Tower installation to version 3.3.3 or later.
- collector/nvd-index
- agent/references
- agent/weakness
- agent/severity
- agent/author
- agent/type
- agent/description
- agent/event
- agent/last-modified-date
- agent/tags
- agent/first-publish-date
- agent/softwarecombine
- collector/mitre-cve
- source/MITRE
- vendor/redhat
- canonical/redhat ansible tower