{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-14329 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-14329 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-14329 is a low-severity vulnerability in Redhat Ansible Tower, published on 27 May 2021. 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-2020-14329 and fix it if it is affected.\n\nWhat it is: CVE-2020-14329 is a low-severity vulnerability in Redhat Ansible Tower, published on 27 May 2021. 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-2020-14329 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-2020-14329/ (Markdown: https://insights.sbomify.com/CVE-2020-14329/index.md)","id":"CVE-2020-14329","markdown":"https://insights.sbomify.com/CVE-2020-14329/index.md","name":"CVE-2020-14329","record":{"aliases":["GHSA-c7r9-mwvj-rr98"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ansible Tower","requires_auth":"low_privilege","summary":"Attackers can retrieve sensitive label and organization data from other organizations via the API, compromising confidentiality.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"ansible_tower","vendor":"redhat"}],"cvss":{"score":3.3,"severity":"low","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"A data exposure flaw was found in Ansible Tower in versions before 3.7.2, where sensitive data can be exposed from the /api/v2/labels/ endpoint. This flaw allows users from other organizations in the system to retrieve any label from the organization and also disclose organization names. The highest threat from this vulnerability is to confidentiality.","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":"Information disclosure in Tower","id":"CVE-2020-14329","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"redhat:ansible_tower","products":["redhat:ansible_tower"],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Improper Output Neutralization and Improper Encoding or Escaping of Output for Logs in ansible","id":"CVE-2020-14330"},"packages":[],"prev":{"headline":"Server-side request forgery in Tower","id":"CVE-2020-14328"},"products":["Tower"],"published":"2021-05-27","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"},{"cvss_score":7.3,"headline":"Misconfiguration in Tower","id":"CVE-2018-16879","kev_date_added":null,"published":"2019-01-03"}],"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-04","vendors":["n/a"]},"summary":"Attackers can retrieve sensitive label and organization data from other organizations via the API, compromising confidentiality.","url":"https://insights.sbomify.com/CVE-2020-14329/"}