dbcve.org
FreeBSDOperating system

CVE-2006-4304

HIGH · 10.0 CVSS v2.0 Published 2006-08-24
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis

A detailed technical summary for this CVE is being prepared.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FreeBSDOperating system
Affected:= 4.11= 5.3= 5.4= 5.5= 6.0= 6.1
NetbsdOperating system
Affected:= 2.0= 3.0= 4.0
OpenBSDOperating system
Affected:= 3.8= 3.9

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch secunia.com →
Recommended fix High confidence

For FreeBSD: upgrade to FreeBSD 13.x or 14.x (current stable); For NetBSD: upgrade to NetBSD 9.x or current; For OpenBSD: upgrade to OpenBSD 7.x (current stable)

  1. 1. Identify the currently running FreeBSD, NetBSD, or OpenBSD version and confirm it matches the affected versions (FreeBSD 4.11-6.1, NetBSD 2.0-4.0 beta before 20060823, OpenBSD 3.8-3.9 before 20060902)
  2. 2. For FreeBSD: Backup all critical data and configuration files (/etc, /var, /home)
  3. 3. For FreeBSD: Plan migration to a supported FreeBSD stable branch (FreeBSD 13.x or 14.x are currently supported)
  4. 4. For NetBSD: Plan migration to a supported NetBSD release (NetBSD 9.x or current)
  5. 5. For OpenBSD: Plan migration to a supported OpenBSD release (OpenBSD 7.x is currently supported)
  6. 6. Perform a fresh installation of the target supported version on replacement hardware
  7. 7. Restore configurations and services, ensuring sppp/ppp-related configurations are tested
  8. 8. Apply all available security updates to the new system
Caveat These are legacy systems from 2006 that are now end-of-life. Full system migration is required - this is not a simple in-place upgrade. All applications and services will need to be reconfigured or rebuilt for the new OS version. Hardware compatibility should be verified for modern components.

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2006-4304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-4304 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data