{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1812 exists.","fix":"No fix has been published for CVE-2002-1812 yet. Limit exposure of the affected software until one is available.","what":"CVE-2002-1812 is a high-severity memory corruption vulnerability in n/a, published on 28 Jun 2005. 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-2002-1812 and fix it if it is affected.\n\nWhat it is: CVE-2002-1812 is a high-severity memory corruption vulnerability in n/a, published on 28 Jun 2005. 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2002-1812 exists.\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-2002-1812/ (Markdown: https://insights.sbomify.com/CVE-2002-1812/index.md)","id":"CVE-2002-1812","markdown":"https://insights.sbomify.com/CVE-2002-1812/index.md","name":"CVE-2002-1812","record":{"aliases":["GHSA-cpmg-jh9h-vghm"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"gdam123 utility","requires_auth":"none","summary":"Local attackers can execute arbitrary code via a buffer overflow in gdam123 by providing a long filename parameter.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"gdam","vendor":"gdam"}],"cvss":{"score":7.2,"severity":"high","source":"nvd","vector":"AV:L/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Buffer overflow in gdam123 0.933 and 0.942 allows local users to execute arbitrary code via a long filename parameter.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2002-08-24","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2002-08-24","kind":"exploitdb","ref":"21760","stars":null,"title":"GDAM123 0.933/0.942 - Filename Buffer Overflow"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2002-1812","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2002"},"n_packages":0,"n_references":4,"next":{"headline":"Path traversal in n/a","id":"CVE-2002-1813"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2002-1811"},"products":["n/a"],"published":"2005-06-28","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":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-08","vendors":["n/a"]},"summary":"Local attackers can execute arbitrary code via a buffer overflow in gdam123 by providing a long filename parameter.","url":"https://insights.sbomify.com/CVE-2002-1812/"}