{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2021-3681 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-3681 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-3681 is a medium-severity vulnerability in ansible, published on 18 Apr 2022. 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-2021-3681 and fix it if it is affected.\n\nWhat it is: CVE-2021-3681 is a medium-severity vulnerability in ansible, published on 18 Apr 2022. 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-2021-3681 in the wild and no public exploit code.\n\nAffected product: ansible. 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-2021-3681/ (Markdown: https://insights.sbomify.com/CVE-2021-3681/index.md)","id":"CVE-2021-3681","markdown":"https://insights.sbomify.com/CVE-2021-3681/index.md","name":"CVE-2021-3681","record":{"aliases":["GHSA-wh68-r6p4-7cv3"],"analysis":{"component_type":"developer_tool","fix_type":"configuration_change","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Ansible Galaxy Collections","requires_auth":"low_privilege","summary":"Manual collection builds may leak sensitive API keys and secrets if not explicitly excluded, exposing them to anyone downloading the published collection.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"ansible_automation_platform","vendor":"redhat"},{"product":"ansible_galaxy","vendor":"redhat"}],"cvss":{"score":5.5,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-522","name":"Insufficiently Protected Credentials"}],"description":"A flaw was found in Ansible Galaxy Collections. When collections are built manually, any files in the repository directory that are not explicitly excluded via the ``build_ignore`` list in \"galaxy.yml\" include files in the ``.tar.gz`` file. This contains sensitive info, such as the user's Ansible Galaxy API key and any secrets in ``ansible`` or ``ansible-playbook`` verbose output without the``no_log`` redaction. Currently, there is no way to deprecate a Collection Or delete a Collection Version. Once published, anyone who downloads or installs the collection can view the secrets.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in ansible","id":"CVE-2021-3681","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Use after free in QEMU","id":"CVE-2021-3682"},"packages":[],"prev":{"headline":"Missing Cryptographic Step in star7th/showdoc","id":"CVE-2021-3680"},"products":["ansible"],"published":"2022-04-18","related":[{"cvss_score":8.8,"headline":"Privilege escalation in ansible-tower","id":"CVE-2021-4112","kev_date_added":null,"published":"2022-08-25"},{"cvss_score":7.3,"headline":"Platform: ec2_key module prints out the private key directly to the standard output","id":"CVE-2023-4237","kev_date_added":null,"published":"2023-10-04"},{"cvss_score":7.1,"headline":"Improper Input Validation and Command Injection in Ansible","id":"CVE-2021-3583","kev_date_added":null,"published":"2021-09-22"},{"cvss_score":6.7,"headline":"Event-driven-ansible: event stream test mode exposes sensitive headers in aap eda","id":"CVE-2025-9907","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":6.7,"headline":"Event-driven-ansible: sensitive internal headers disclosure in aap eda event streams","id":"CVE-2025-9908","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":6.7,"headline":"Aap-gateway: improper path validation in gateway allows credential exfiltration","id":"CVE-2025-9909","kev_date_added":null,"published":"2026-02-27"},{"cvss_score":6.5,"headline":"Privilege escalation in Red Hat Ansible Automation Platform","id":"CVE-2022-2568","kev_date_added":null,"published":"2022-08-18"}],"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-03","vendors":["n/a"]},"summary":"Manual collection builds may leak sensitive API keys and secrets if not explicitly excluded, exposing them to anyone downloading the published collection.","url":"https://insights.sbomify.com/CVE-2021-3681/"}