# CVE-2008-4404: Denial of service in n/a

> Remote attackers can spoof IPv6 Neighbor Discovery messages to cause denial of service or read private network traffic on IBM zSeries servers.

- **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:** 3 Oct 2008
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-5c8h-74jm-rr6m

## What is CVE-2008-4404?

CVE-2008-4404 is a critical denial of service vulnerability in n/a, published on 3 Oct 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The IPv6 Neighbor Discovery Protocol (NDP) implementation on IBM zSeries servers 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), a related issue to CVE-2008-2476.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2008-4404?

It affects 1 product.


Products: Ibm Zseries.

## How do I fix CVE-2008-4404?

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

## Is CVE-2008-4404 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-4404 and fix it if it is affected.

What it is: CVE-2008-4404 is a critical denial of service vulnerability in n/a, published on 3 Oct 2008. 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-2008-4404 in the wild and no public exploit code.

Affected product: n/a. 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-2008-4404/ (Markdown: https://insights.sbomify.com/CVE-2008-4404/index.md)
```

## Sources

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

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