{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-25125 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-25125 is a high-severity memory corruption vulnerability in n/a, published on 3 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-25125 and fix it if it is affected.\n\nWhat it is: CVE-2020-25125 is a high-severity memory corruption vulnerability in n/a, published on 3 Sep 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-25125 in the wild and no public exploit code.\n\nAffected product: n/a. 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-25125/ (Markdown: https://insights.sbomify.com/CVE-2020-25125/index.md)","id":"CVE-2020-25125","markdown":"https://insights.sbomify.com/CVE-2020-25125/index.md","name":"CVE-2020-25125","record":{"aliases":["ALPINE-CVE-2020-25125","CLEANSTART-2026-SR17616","GHSA-g8h3-hp92-c5qx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GnuPG encryption library","requires_auth":"none","summary":"An attacker can cause a crash in GnuPG by tricking a user into importing a malicious OpenPGP key with AEAD preferences.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gnupg","vendor":"gnupg"},{"product":"gpg4win","vendor":"gpg4win"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"GnuPG 2.2.21 and 2.2.22 (and Gpg4win 3.1.12) has an array overflow, leading to a crash or possibly unspecified other impact, when a victim imports an attacker's OpenPGP key, and this key has AEAD preferences. The overflow is caused by a g10/key-check.c error. NOTE: GnuPG 2.3.x is unaffected. GnuPG 2.2.23 is a fixed version.","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":"Memory corruption in n/a","id":"CVE-2020-25125","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":6,"next":{"headline":"SQL injection in n/a","id":"CVE-2020-25130"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2020-25124"},"products":["n/a"],"published":"2020-09-03","related":[{"cvss_score":9.8,"headline":"Integer overflow in libksba","id":"CVE-2022-3515","kev_date_added":null,"published":"2023-01-12"},{"cvss_score":9.3,"headline":"Memory corruption in n/a","id":"CVE-2008-1530","kev_date_added":null,"published":"2008-03-27"},{"cvss_score":8.4,"headline":"Memory corruption in GnuPG","id":"CVE-2026-24882","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":8.1,"headline":"Memory corruption in GnuPG","id":"CVE-2026-24881","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":7.8,"headline":"Memory corruption in GnuPG","id":"CVE-2025-68973","kev_date_added":null,"published":"2025-12-28"},{"cvss_score":6.8,"headline":"Memory corruption in n/a","id":"CVE-2006-6169","kev_date_added":null,"published":"2006-11-29"}],"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":"An attacker can cause a crash in GnuPG by tricking a user into importing a malicious OpenPGP key with AEAD preferences.","url":"https://insights.sbomify.com/CVE-2020-25125/"}