# CVE-2007-2242: Denial of service in n/a

> Remote attackers can cause denial of service via crafted IPv6 type 0 route headers, affecting operating systems with IPv6 support.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w3ph-xq76-6prc

## What is CVE-2007-2242?

CVE-2007-2242 is a high-severity denial of service vulnerability in n/a, published on 25 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The IPv6 protocol allows remote attackers to cause a denial of service via crafted IPv6 type 0 route headers (IPV6_RTHDR_TYPE_0) that create network amplification between two routers.

## Which versions are affected by CVE-2007-2242?

It affects 1 product.


Products: Ietf Ipv6.

## How do I fix CVE-2007-2242?

Apply the vendor's patch.

## Is CVE-2007-2242 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-10142](https://insights.sbomify.com/CVE-2016-10142/): Denial of service in n/a (high 8.6)
- [CVE-2025-23018](https://insights.sbomify.com/CVE-2025-23018/): Security feature bypass in IPv6 (medium 5.4)
- [CVE-2025-23019](https://insights.sbomify.com/CVE-2025-23019/): Other in IPv6 (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2242 and fix it if it is affected.

What it is: CVE-2007-2242 is a high-severity denial of service vulnerability in n/a, published on 25 Apr 2007. 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-2007-2242 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-2007-2242/ (Markdown: https://insights.sbomify.com/CVE-2007-2242/index.md)
```

## Sources

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

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