# CVE-2008-0177: Null dereference in n/a

> Remote attackers can crash the system via a crafted IPv6 IPComp packet due to improper return value checking in the KAME IPComp input handler.

- **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:** No
- **Published:** 7 Feb 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vrv9-xcjr-98wp

## What is CVE-2008-0177?

CVE-2008-0177 is a high-severity vulnerability in n/a, published on 7 Feb 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ipcomp6_input function in sys/netinet6/ipcomp_input.c in the KAME project before 20071201 does not properly check the return value of the m_pulldown function, which allows remote attackers to cause a denial of service (system crash) via an IPv6 packet with an IPComp header.

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

It affects 1 product.


Products: Kame Ipcomp.

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

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

## Is CVE-2008-0177 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0177 exists.

Public exploit code:

- Apple Mac OSX xnu 1228.3.13 - IPv6-ipcomp Remote kernel Denial of Service (PoC) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-0177 is a high-severity vulnerability in n/a, published on 7 Feb 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-0177 exists.

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-0177/ (Markdown: https://insights.sbomify.com/CVE-2008-0177/index.md)
```

## Sources

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

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