{"answers":{"affected":"3 open source packages ship an affected version, including ansible. It affects 2 products.","exploited":"There is no known exploitation of CVE-2022-3697 in the wild and no public exploit code.","fix":"Upgrade ansible to 7.0.0 or later.","what":"CVE-2022-3697 is a high-severity vulnerability in ansible, ansible community.aws, ansible amazon.aws, published on 28 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-3697 and fix it if it is affected.\n\nWhat it is: CVE-2022-3697 is a high-severity vulnerability in ansible, ansible community.aws, ansible amazon.aws, published on 28 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-3697 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ansible (PyPI): affected from 2.5.0; fixed in 7.0.0\n- ansible (PyPI): affected from 2.5.0; fixed in 7.0.0\n- ansible (PyPI): affected from 2.5.0; fixed in 7.0.0\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-2022-3697/ (Markdown: https://insights.sbomify.com/CVE-2022-3697/index.md)","id":"CVE-2022-3697","markdown":"https://insights.sbomify.com/CVE-2022-3697/index.md","name":"CVE-2022-3697","record":{"aliases":["CLSA-2023-1691083401","DEBIAN-CVE-2022-3697","GHSA-cpx3-93w7-457x","PYSEC-2026-768","UBUNTU-CVE-2022-3697"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Ansible AWS collection","requires_auth":"none","summary":"An attacker can read leaked passwords from logs due to insecure handling of the tower_callback parameter in the Ansible amazon.aws ec2_instance module.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"ansible","vendor":"redhat"},{"product":"ansible_collection","vendor":"redhat"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-233","name":"Improper Handling of Parameters"}],"description":"A flaw was found in Ansible in the amazon.aws collection when using the tower_callback parameter from the amazon.aws.ec2_instance module. This flaw allows an attacker to take advantage of this issue as the module is handling the parameter insecurely, leading to the password leaking in the logs.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Ansible leaks password to logs","id":"CVE-2022-3697","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":3,"n_references":2,"next":{"headline":"Denial of service in Diagnostics","id":"CVE-2022-3698"},"packages":[{"ecosystem":"PyPI","fixed":["7.0.0"],"introduced":["2.5.0"],"last_affected":[],"package":"ansible","purl":null,"source":"GHSA-cpx3-93w7-457x"},{"ecosystem":"PyPI","fixed":["7.0.0"],"introduced":["2.5.0"],"last_affected":[],"package":"ansible","purl":"pkg:pypi/ansible","source":"GHSA-cpx3-93w7-457x"},{"ecosystem":"PyPI","fixed":["7.0.0"],"introduced":["2.5.0"],"last_affected":[],"package":"ansible","purl":"pkg:pypi/ansible","source":"PYSEC-2026-768"}],"prev":{"headline":"Code injection in Sophos Firewall","id":"CVE-2022-3696"},"products":["ansible, ansible community.aws, ansible amazon.aws"],"published":"2022-10-28","related":[{"cvss_score":9.8,"headline":"Ansible Remote Code Execution","id":"CVE-2014-4657","kev_date_added":null,"published":"2020-02-20"},{"cvss_score":9.8,"headline":"Ansible Arbitrary Code Execution","id":"CVE-2014-4966","kev_date_added":null,"published":"2020-02-18"},{"cvss_score":9.8,"headline":"Ansible Arbitrary Code Execution","id":"CVE-2014-4967","kev_date_added":null,"published":"2020-02-18"},{"cvss_score":9.8,"headline":"Ansible Insertion of Sensitive Information into Log File vulnerability","id":"CVE-2017-7550","kev_date_added":null,"published":"2017-11-21"},{"cvss_score":8.8,"headline":"Ansible Arbitrary Code Execution","id":"CVE-2014-3498","kev_date_added":null,"published":"2017-06-08"},{"cvss_score":8,"headline":"Ansible Arbitrary Code Execution","id":"CVE-2017-7466","kev_date_added":null,"published":"2018-06-22"},{"cvss_score":7.8,"headline":"Ansible Sandbox Escape via Symlink Attack","id":"CVE-2015-6240","kev_date_added":null,"published":"2017-06-07"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"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":"2025-02-13","vendors":["n/a"]},"summary":"An attacker can read leaked passwords from logs due to insecure handling of the tower_callback parameter in the Ansible amazon.aws ec2_instance module.","url":"https://insights.sbomify.com/CVE-2022-3697/"}