{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-25646 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-25646 is a high-severity vulnerability in Ansible Community Community Collections, published on 29 Oct 2020. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-25646 and fix it if it is affected.\n\nWhat it is: CVE-2020-25646 is a high-severity vulnerability in Ansible Community Community Collections, published on 29 Oct 2020. 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-2020-25646 in the wild and no public exploit code.\n\nAffected product: Ansible Community Community Collections. 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-25646/ (Markdown: https://insights.sbomify.com/CVE-2020-25646/index.md)","id":"CVE-2020-25646","markdown":"https://insights.sbomify.com/CVE-2020-25646/index.md","name":"CVE-2020-25646","record":{"aliases":["ALPINE-CVE-2020-25646","CLEANSTART-2026-WL91519","GHSA-92hf-4chr-8hrf","UBUNTU-CVE-2020-25646"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Ansible crypto collection","requires_auth":"none","summary":"Attackers can read private keys from logs due to improper output handling in the Ansible community.crypto collection.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"community.crypto","vendor":"ansible_collections_project"}],"cvss":{"score":7.5,"severity":"high","source":"cna","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-116","name":"Improper Encoding or Escaping of Output"},{"id":"CWE-117","name":"Improper Output Neutralization for Logs"}],"description":"A flaw was found in Ansible Collection community.crypto. openssl_privatekey_info exposes private key in logs. This directly impacts 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":true,"headline":"Information disclosure in Community Collections","id":"CVE-2020-25646","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in grub2","id":"CVE-2020-25647"},"packages":[],"prev":{"headline":"Information disclosure in kernel","id":"CVE-2020-25645"},"products":["Community Collections"],"published":"2020-10-29","related":[],"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":["Ansible Community"]},"summary":"Attackers can read private keys from logs due to improper output handling in the Ansible community.crypto collection.","url":"https://insights.sbomify.com/CVE-2020-25646/"}