# CVE-2006-4304: Memory corruption in n/a

> Remote attackers can trigger a buffer overflow in the sppp driver via crafted LCP packets, leading to code execution, system panic, or information disclosure.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2p53-823g-x3xx

## What is CVE-2006-4304?

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.

### Official 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.

## Which versions are affected by CVE-2006-4304?

It affects 3 products.


Products: Freebsd Freebsd, Netbsd Netbsd, Openbsd Openbsd.

## How do I fix CVE-2006-4304?

No fix has been published for CVE-2006-4304 yet. Limit exposure of the affected software until one is available.

## Is CVE-2006-4304 being exploited?

There is no known exploitation of CVE-2006-4304 in the wild and no public exploit code.

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0)
- [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0)
- [CVE-2001-0969](https://insights.sbomify.com/CVE-2001-0969/): Security feature bypass in n/a (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4304 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2006-4304 in the wild and no public exploit code.

Affected product: Freebsd Freebsd. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2006-4304/ (Markdown: https://insights.sbomify.com/CVE-2006-4304/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2006-4304
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2006-4304
- OSV: https://osv.dev/vulnerability/CVE-2006-4304

---
From sbomify Insights: https://insights.sbomify.com/CVE-2006-4304/
Summaries are generated and may contain mistakes; the official description above is the record.