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

> Remote attackers can cause a denial of service on Cisco ASA and PIX security appliances by sending a crafted IPv6 packet, requiring immediate patching.

- **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:** 23 Oct 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qwq8-q6w3-gwm5

## What is CVE-2008-3816?

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

### Official description

Unspecified vulnerability in Cisco Adaptive Security Appliances (ASA) 5500 Series and PIX Security Appliances 7.2(4)9 and 7.2(4)10 allows remote attackers to cause a denial of service (device reload) via a crafted IPv6 packet.

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

It affects 2 products.


Products: Cisco Adaptive Security Appliance 5500 Series, Cisco Pix Security Appliance.

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

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

## Is CVE-2008-3816 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3817](https://insights.sbomify.com/CVE-2008-3817/): Denial of service in n/a (high 7.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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