{"answers":{"affected":"It affects 6 products.","exploited":"There is no known exploitation of CVE-2012-3899 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2012-3899 yet. Limit exposure of the affected software until one is available.","what":"CVE-2012-3899 is a medium-severity memory corruption vulnerability in n/a, published on 16 Sep 2012. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2012-3899 and fix it if it is affected.\n\nWhat it is: CVE-2012-3899 is a medium-severity memory corruption vulnerability in n/a, published on 16 Sep 2012. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2012-3899 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-2012-3899/ (Markdown: https://insights.sbomify.com/CVE-2012-3899/index.md)","id":"CVE-2012-3899","markdown":"https://insights.sbomify.com/CVE-2012-3899/index.md","name":"CVE-2012-3899","record":{"aliases":["GHSA-p75j-c4gv-8vx8"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Cisco IPS sensor","requires_auth":"none","summary":"Remote attackers can cause a denial of service and traffic-inspection outage on Cisco IPS sensors via crafted network traffic due to improper memory allocation.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"intrusion_prevention_system","vendor":"cisco"},{"product":"ips_4240","vendor":"cisco"},{"product":"ips_4250_sx","vendor":"cisco"},{"product":"ips_4255","vendor":"cisco"},{"product":"ips_4260","vendor":"cisco"},{"product":"ips_4270-20","vendor":"cisco"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:N/I:N/A:P","version":"2.0"},"cwes":[{"id":"CWE-399","name":null}],"description":"sensorApp on Cisco IPS 4200 series sensors 6.0, 6.2, and 7.0 does not properly allocate memory, which allows remote attackers to cause a denial of service (memory corruption and process crash, and traffic-inspection outage) via network traffic, aka Bug ID CSCtn23051.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Memory corruption in n/a","id":"CVE-2012-3899","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2012"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service in n/a","id":"CVE-2012-3901"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2012-3895"},"products":["n/a"],"published":"2012-09-16","related":[{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2013-3410","kev_date_added":null,"published":"2013-07-18"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2008-2060","kev_date_added":null,"published":"2008-06-18"},{"cvss_score":7.1,"headline":"Race condition in n/a","id":"CVE-2015-0654","kev_date_added":null,"published":"2015-03-13"},{"cvss_score":7.1,"headline":"Race condition in n/a","id":"CVE-2014-3406","kev_date_added":null,"published":"2014-10-19"},{"cvss_score":6.8,"headline":"Denial of service in n/a","id":"CVE-2014-2103","kev_date_added":null,"published":"2014-02-27"},{"cvss_score":5,"headline":"Denial of service in n/a","id":"CVE-2014-3402","kev_date_added":null,"published":"2014-10-10"}],"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-09-17","vendors":["n/a"]},"summary":"Remote attackers can cause a denial of service and traffic-inspection outage on Cisco IPS sensors via crafted network traffic due to improper memory allocation.","url":"https://insights.sbomify.com/CVE-2012-3899/"}