# CVE-2004-0674: Denial of service in n/a

> Remote attackers can crash Enterasys XSR-1800 routers by sending packets with IP record route option when Policy-Based Routing is enabled.

- **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:** 13 Jul 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hm5g-328c-98gp

## What is CVE-2004-0674?

CVE-2004-0674 is a medium-severity denial of service vulnerability in n/a, published on 13 Jul 2004. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Enterasys XSR-1800 series Security Routers, when running firmware 7.0.0.0 and using Policy-Based Routing, allow remote attackers to cause a denial of service (crash) via a packet with the IP record route option set.

## Which versions are affected by CVE-2004-0674?

It affects 3 products.


Products: Enterasys Xsr-1805, Enterasys Xsr-1850, Enterasys Xsr-3000.

## How do I fix CVE-2004-0674?

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

## Is CVE-2004-0674 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0674 and fix it if it is affected.

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

## Sources

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

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