{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-16879 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-16879 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-16879 is a high-severity vulnerability in Redhat Ansible Tower, published on 3 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-16879 and fix it if it is affected.\n\nWhat it is: CVE-2018-16879 is a high-severity vulnerability in Redhat Ansible Tower, published on 3 Jan 2019. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-16879 in the wild and no public exploit code.\n\nAffected product: Redhat Ansible Tower. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-16879/ (Markdown: https://insights.sbomify.com/CVE-2018-16879/index.md)","id":"CVE-2018-16879","markdown":"https://insights.sbomify.com/CVE-2018-16879/index.md","name":"CVE-2018-16879","record":{"aliases":["GHSA-xw9p-c763-93fq"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ansible Tower","requires_auth":"low_privilege","summary":"Ansible Tower uses insecure default settings for RabbitMQ messaging, allowing attackers to leak sensitive data or cause denial of service.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"ansible_tower","vendor":"redhat"}],"cvss":{"score":7.3,"severity":"high","source":"cna","vector":"CVSS:3.0/AV:A/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-311","name":"Missing Encryption of Sensitive Data"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Misconfiguration in Tower","id":"CVE-2018-16879","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:ansible_tower","products":["redhat:ansible_tower"],"type":"misconfiguration","year":"2018"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in kernel","id":"CVE-2018-16880"},"packages":[],"prev":{"headline":"Denial of service in pacemaker","id":"CVE-2018-16878"},"products":["Tower"],"published":"2019-01-03","related":[{"cvss_score":8.8,"headline":"Cross-site request forgery in ansible-tower","id":"CVE-2018-10884","kev_date_added":null,"published":"2018-08-22"},{"cvss_score":8.8,"headline":"Code injection in Ansible Tower","id":"CVE-2018-1104","kev_date_added":null,"published":"2018-05-02"},{"cvss_score":8.4,"headline":"Information disclosure in Tower","id":"CVE-2019-14890","kev_date_added":null,"published":"2019-11-26"},{"cvss_score":8.4,"headline":"Code injection in Ansible Tower","id":"CVE-2017-12148","kev_date_added":null,"published":"2018-07-27"},{"cvss_score":8.2,"headline":"Misconfiguration in Tower","id":"CVE-2019-19340","kev_date_added":null,"published":"2019-12-19"},{"cvss_score":8,"headline":"Privilege escalation in Ansible Tower","id":"CVE-2016-7070","kev_date_added":null,"published":"2018-09-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["[UNKNOWN]"]},"summary":"Ansible Tower uses insecure default settings for RabbitMQ messaging, allowing attackers to leak sensitive data or cause denial of service.","url":"https://insights.sbomify.com/CVE-2018-16879/"}