{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2004-2269 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2004-2269 is a high-severity memory corruption vulnerability in n/a, published on 19 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2004-2269 and fix it if it is affected.\n\nWhat it is: CVE-2004-2269 is a high-severity memory corruption vulnerability in n/a, published on 19 Jul 2005. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2004-2269 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-2004-2269/ (Markdown: https://insights.sbomify.com/CVE-2004-2269/index.md)","id":"CVE-2004-2269","markdown":"https://insights.sbomify.com/CVE-2004-2269/index.md","name":"CVE-2004-2269","record":{"aliases":["DEBIAN-CVE-2004-2269","GHSA-h3pw-hrvp-5hmj"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Passive Asset Detection System","requires_auth":"none","summary":"Local attackers can execute arbitrary code via a stack-based buffer overflow in Pads when processing long report file names.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"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":"Stack-based buffer overflow in pads.c in Passive Asset Detection System (Pads) might allow local users to execute arbitrary code via a long report file name argument. NOTE: since Pads is not normally installed setuid, this may not be a vulnerability.","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-2004-2269","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2004"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2004-2270"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2004-2268"},"products":["n/a"],"published":"2005-07-19","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)"}],"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 stack-based buffer overflow in Pads when processing long report file names.","url":"https://insights.sbomify.com/CVE-2004-2269/"}