# CVE-2008-6605: Cross-site request forgery in n/a

> Remote attackers can cause network outages on 2wire routers via CSRF in the xslt script, requiring user interaction to trigger the malicious request.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Apr 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2xf9-2vp2-w4x6

## What is CVE-2008-6605?

CVE-2008-6605 is a medium-severity vulnerability in n/a, published on 6 Apr 2009. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site request forgery (CSRF) vulnerability in the xslt script in the web-based management interface on the 2wire 1701HG, 1800HW, 2071HG, and 2700HG with firmware 3.17.5, 3.7.1, 4.25.19, or 5.29.51 allows remote attackers to hijack the intranet connectivity of arbitrary users for requests that cause a denial of service (network outage) via a page parameter with a % (percent) character followed by a non-alphanumeric character.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 4 products.


Products: 2wire 1701hg, 2wire 1800hw, 2wire 2071hg, 2wire 2700hg.

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

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

## Is CVE-2008-6605 being exploited?

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

Public exploit code:

- 2WIRE DSL Router - 'xslt' Denial of Service (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6605 is a medium-severity vulnerability in n/a, published on 6 Apr 2009. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-6605 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-6605/ (Markdown: https://insights.sbomify.com/CVE-2008-6605/index.md)
```

## Sources

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

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