{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2006-6169 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2006-6169 is a medium-severity memory corruption vulnerability in n/a, published on 29 Nov 2006. 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-2006-6169 and fix it if it is affected.\n\nWhat it is: CVE-2006-6169 is a medium-severity memory corruption vulnerability in n/a, published on 29 Nov 2006. 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-2006-6169 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-2006-6169/ (Markdown: https://insights.sbomify.com/CVE-2006-6169/index.md)","id":"CVE-2006-6169","markdown":"https://insights.sbomify.com/CVE-2006-6169/index.md","name":"CVE-2006-6169","record":{"aliases":["DEBIAN-CVE-2006-6169","GHSA-5xr2-gxmf-xc8r"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"GnuPG encryption tool","requires_auth":"none","summary":"Heap-based buffer overflow in GnuPG allows arbitrary code execution via crafted messages with C-escape expansions during interactive use.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gnupg","vendor":"gnupg"}],"cvss":{"score":6.8,"severity":"medium","source":"nvd","vector":"AV:N/AC:M/Au:N/C:P/I:P/A:P","version":"2.0"},"cwes":[],"description":"Heap-based buffer overflow in the ask_outfile_name function in openfile.c for GnuPG (gpg) 1.4 and 2.0, when running interactively, might allow attackers to execute arbitrary code via messages with \"C-escape\" expansions, which cause the make_printable_string function to return a longer string than expected while constructing a prompt.","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-2006-6169","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2006"},"n_packages":0,"n_references":34,"next":{"headline":"Memory corruption in n/a","id":"CVE-2006-6170"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2006-6168"},"products":["n/a"],"published":"2006-11-29","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":7.8,"headline":"Memory corruption in n/a","id":"CVE-2020-25125","kev_date_added":null,"published":"2020-09-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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-07","vendors":["n/a"]},"summary":"Heap-based buffer overflow in GnuPG allows arbitrary code execution via crafted messages with C-escape expansions during interactive use.","url":"https://insights.sbomify.com/CVE-2006-6169/"}