# CVE-2001-1194: Denial of service in n/a

> Remote attackers can crash Zyxel SDSL routers by sending malformed IP packets or oversized fragmented packets, causing a denial of service.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Mar 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-2xmv-96h9-88qv

## What is CVE-2001-1194?

CVE-2001-1194 is a medium-severity denial of service vulnerability in n/a, published on 15 Mar 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Zyxel Prestige 681 and 1600 SDSL Routers allow remote attackers to cause a denial of service via malformed packets with (1) an IP length less than actual packet size, or (2) fragmented packets whose size exceeds 64 kilobytes after reassembly.

## Which versions are affected by CVE-2001-1194?

It affects 2 products.


Products: Zyxel Prestige 1600, Zyxel Prestige 681.

## How do I fix CVE-2001-1194?

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

## Is CVE-2001-1194 being exploited?

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

Public exploit code:

- ZYXEL Prestige 681 SDSL Router - IP Fragment Reassembly (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1194 and fix it if it is affected.

What it is: CVE-2001-1194 is a medium-severity denial of service vulnerability in n/a, published on 15 Mar 2002. 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-2001-1194 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-2001-1194/ (Markdown: https://insights.sbomify.com/CVE-2001-1194/index.md)
```

## Sources

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

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