{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2006-4304 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2006-4304 yet. Limit exposure of the affected software until one is available.","what":"CVE-2006-4304 is a critical memory corruption vulnerability in Freebsd Freebsd, published on 24 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2006-4304 and fix it if it is affected.\n\nWhat it is: CVE-2006-4304 is a critical memory corruption vulnerability in Freebsd Freebsd, published on 24 Aug 2006. 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-2006-4304 in the wild and no public exploit code.\n\nAffected product: Freebsd Freebsd. 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-4304/ (Markdown: https://insights.sbomify.com/CVE-2006-4304/index.md)","id":"CVE-2006-4304","markdown":"https://insights.sbomify.com/CVE-2006-4304/index.md","name":"CVE-2006-4304","record":{"aliases":["GHSA-2p53-823g-x3xx"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["code_execution","denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"BSD kernel network driver","requires_auth":"none","summary":"Remote attackers can trigger a buffer overflow in the sppp driver via crafted LCP packets, leading to code execution, system panic, or information disclosure.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"freebsd","vendor":"freebsd"},{"product":"netbsd","vendor":"netbsd"},{"product":"openbsd","vendor":"openbsd"}],"cvss":{"score":10,"severity":"critical","source":"nvd","vector":"AV:N/AC:L/Au:N/C:C/I:C/A:C","version":"2.0"},"cwes":[],"description":"Buffer overflow in the sppp driver in FreeBSD 4.11 through 6.1, NetBSD 2.0 through 4.0 beta before 20060823, and OpenBSD 3.8 and 3.9 before 20060902 allows remote attackers to cause a denial of service (panic), obtain sensitive information, and possibly execute arbitrary code via crafted Link Control Protocol (LCP) packets with an option length that exceeds the overall length, which triggers the overflow in (1) pppoe and (2) ippp.  NOTE: this issue was originally incorrectly reported for the ppp driver.","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-2006-4304","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"freebsd:freebsd","products":["freebsd:freebsd","netbsd:netbsd","openbsd:openbsd"],"type":"memory_corruption","year":"2006"},"n_packages":0,"n_references":10,"next":{"headline":"Memory corruption in n/a","id":"CVE-2006-4305"},"packages":[],"prev":{"headline":"Race condition in n/a","id":"CVE-2006-4303"},"products":["n/a"],"published":"2006-08-24","related":[{"cvss_score":10,"headline":"Memory corruption in FreeBSD","id":"CVE-2018-17160","kev_date_added":null,"published":"2018-12-04"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2014-3954","kev_date_added":null,"published":"2014-10-27"},{"cvss_score":10,"headline":"Integer overflow in n/a","id":"CVE-2006-0226","kev_date_added":null,"published":"2006-01-19"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-2004-0002","kev_date_added":null,"published":"2004-02-03"},{"cvss_score":10,"headline":"Security feature bypass in n/a","id":"CVE-2001-0969","kev_date_added":null,"published":"2002-03-09"},{"cvss_score":10,"headline":"Denial of service in n/a","id":"CVE-2001-0388","kev_date_added":null,"published":"2001-09-18"}],"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":"Remote attackers can trigger a buffer overflow in the sppp driver via crafted LCP packets, leading to code execution, system panic, or information disclosure.","url":"https://insights.sbomify.com/CVE-2006-4304/"}