# CVE-2006-1670: Denial of service in n/a

> Remote attackers can cause denial of service on Cisco ONS 15000 nodes by sending invalid responses, leading to memory exhaustion or card resets.

- **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 Apr 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-f8cr-xgwc-mr3c

## What is CVE-2006-1670?

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

### Official description

Control cards for Cisco Optical Networking System (ONS) 15000 series nodes before 20060405 allow remote attackers to cause a denial of service (memory exhaustion and possibly card reset) by sending an invalid response when the final ACK is expected, aka bug ID CSCei45910.

## Which versions are affected by CVE-2006-1670?

It affects 5 products.


Products: Cisco Ons 15310-Cl Series, Cisco Ons 15454 Mspp, Cisco Ons 15454 Mstp, Cisco Ons 15600, Cisco Optical Networking Systems Software.

## How do I fix CVE-2006-1670?

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

## Is CVE-2006-1670 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-1672](https://insights.sbomify.com/CVE-2006-1672/): Code injection in n/a (high 7.5)
- [CVE-2006-1671](https://insights.sbomify.com/CVE-2006-1671/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-1670 and fix it if it is affected.

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

## Sources

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

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