{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2022 exists.","fix":"No fix has been published for CVE-2004-2022 yet. Limit exposure of the affected software until one is available.","what":"CVE-2004-2022 is a low-severity memory corruption vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2004-2022 and fix it if it is affected.\n\nWhat it is: CVE-2004-2022 is a low-severity memory corruption vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2022 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-2004-2022/ (Markdown: https://insights.sbomify.com/CVE-2004-2022/index.md)","id":"CVE-2004-2022","markdown":"https://insights.sbomify.com/CVE-2004-2022/index.md","name":"CVE-2004-2022","record":{"aliases":["CVE-2004-2285","GHSA-6g7x-c8vf-63fq"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Perl interpreter","requires_auth":"none","summary":"Attackers can cause a crash or execute arbitrary code via a stack-based buffer overflow in Perl's system command handling on Windows.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"activeperl","vendor":"activestate"}],"cvss":{"score":2.1,"severity":"low","source":"nvd","vector":"AV:L/AC:L/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[],"description":"ActivePerl 5.8.x and others, and Larry Wall's Perl 5.6.1 and others, when running on Windows systems, allows attackers to cause a denial of service (crash) and possibly execute arbitrary code via a long argument to the system command, which leads to a stack-based buffer overflow.  NOTE: it is unclear whether this bug is in Perl or the OS API that is used by Perl.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2004-05-18","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2004-05-18","kind":"exploitdb","ref":"24128","stars":null,"title":"ActivePerl 5.x / Cygwin 1.5.x - System Function Call Buffer Overflow"}],"tier":"weaponised"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2004-2022","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2004"},"n_packages":0,"n_references":9,"next":{"headline":"SQL injection in n/a","id":"CVE-2004-2023"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2004-2021"},"products":["n/a"],"published":"2005-05-10","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2004-0377","kev_date_added":null,"published":"2004-04-06"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2004-2286","kev_date_added":null,"published":"2005-08-04"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2001-0815","kev_date_added":null,"published":"2002-03-09"},{"cvss_score":6,"headline":"Privilege escalation in n/a","id":"CVE-2012-5377","kev_date_added":null,"published":"2012-10-11"},{"cvss_score":4.6,"headline":"Privilege escalation in n/a","id":"CVE-2006-2856","kev_date_added":null,"published":"2006-06-06"}],"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":"Attackers can cause a crash or execute arbitrary code via a stack-based buffer overflow in Perl's system command handling on Windows.","url":"https://insights.sbomify.com/CVE-2004-2022/"}