FreeBSDOperating system

CVE-2008-2476

HIGH · 9.3 CVSS v2.0 Published 2008-10-03

Fix available

A fix is available. Upgrade to after 6.4 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The IPv6 Neighbor Discovery Protocol (NDP) implementation in (1) FreeBSD 6.3 through 7.1, (2) OpenBSD 4.2 and 4.3, (3) NetBSD, (4) Force10 FTOS before E7.7.1.1, (5) Juniper JUNOS, and (6) Wind River VxWorks 5.x through 6.4 does not validate the origin of Neighbor Discovery messages, which allows remote attackers to cause a denial of service (loss of connectivity) or read private network traffic via a spoofed message that modifies the Forward Information Base (FIB).

Technical summary

dbcve analysis · high confidence

The IPv6 Neighbor Discovery Protocol (NDP) implementation in multiple BSD variants and network devices fails to validate the origin of Neighbor Discovery messages, allowing remote attackers to spoof NDP messages and modify the Forward Information Base (FIB). This enables denial of service through connectivity loss or interception of private network traffic.

MitigationApply vendor-supplied patches or firmware updates for affected systems (FreeBSD 6.3-7.1, OpenBSD 4.2-4.3, NetBSD, Force10 FTOS before E7.7.1.1, Juniper JUNOS, Wind River VxWorks 5.x-6.4). Where patches are unavailable, consider disabling IPv6 or implementing router advertisement filtering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

FreeBSDOperating system

Affected:= 6.3= 7.1

FtosOperating system

Affected:all versions

JnosOperating system

Affected:all versions

NetbsdOperating system

Affected:all versions

OpenBSDOperating system

Affected:= 4.2= 4.3

VxworksOperating system

Affected:<= 6.4= 5= 5.5

CVSS breakdown

From the vector

Attack vector: Network
Complexity: M
Authentication: None
Confidentiality: Complete
Integrity: Complete
Availability: Complete

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

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Identify operating system and version

Run 'uname -a' or check system documentation to determine the exact OS version

Affected if The system is running FreeBSD 6.3, FreeBSD 7.1, OpenBSD 4.2, OpenBSD 4.3, NetBSD any version, Force10 FTOS any version, Juniper JUNOS any version, or Wind River VxWorks 5.x through 6.4 (including versions 5, 5.5, and versions <= 6.4)
Verify IPv6 is enabled

Check system network configuration for active IPv6 interfaces using 'ifconfig -a' or equivalent command for the platform

Affected if IPv6 is actively enabled and configured on the system (the vulnerability only affects systems using IPv6)
Confirm system role as IPv6 router

Check if the system is configured to route IPv6 traffic or participate in Neighbor Discovery (look for router advertisement daemon, IPv6 forwarding, or NDP-related processes)

Affected if The system acts as an IPv6 router or is a network device that processes NDP messages and maintains a Forward Information Base (FIB) for IPv6 routes

You are affected if you are running any of the listed affected versions/platforms AND have IPv6 enabled AND the system processes NDP messages as a router or network device.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Upgrade available Upgrade to a release after 6.4

Interim mitigation

Apply vendor-supplied patches or firmware updates for affected systems (FreeBSD 6.3-7.1, OpenBSD 4.2-4.3, NetBSD, Force10 FTOS before E7.7.1.1, Juniper JUNOS, Wind River VxWorks 5.x-6.4). Where patches are unavailable, consider disabling IPv6 or implementing router advertisement filtering.

Fix this in FreeBSD Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing6.0 h
Review / QA3.0 h

21.0 hours of engineering $3,680

Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2008-2476 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2008-2476?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 6.4 or later

Severity 9.3 High

Exploit likelihood EPSS, next 30 days 7.4%

Affects: FreeBSD

Remediation

A high-priority fix

Fix this in FreeBSD 21 hrs · High

Typical engagement from $3,680

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2008-2476 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References