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

> Remote attackers can hijack administrator sessions to execute commands, change credentials, or alter network settings via CSRF in DD-WRT.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Aug 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mxf4-vppx-9gvw

## What is CVE-2008-6974?

CVE-2008-6974 is a medium-severity vulnerability in n/a, published on 14 Aug 2009. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in apply.cgi in DD-WRT 24 sp1 and earlier allow remote attackers to hijack the authentication of administrators for requests that (1) execute arbitrary commands via the ping_ip parameter; (2) change the administrative credentials via the http_username and http_passwd parameters; (3) enable remote administration via the remote_management parameter; or (4) configure port forwarding via certain from, to, ip, and pro parameters.

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

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

It affects 1 product.


Products: Dd-Wrt Dd-Wrt.

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

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

## Is CVE-2008-6974 being exploited?

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

Public exploit code:

- DD-WRT v24-sp1 - Cross-Site Reference Forgery (exploitdb)
- DD-WRT HTTPd Daemon/Service - Remote Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2021-27137](https://insights.sbomify.com/CVE-2021-27137/): DD-WRT Stack-Based Buffer Overflow (high 8.1, exploited in the wild)
- [CVE-2020-13976](https://insights.sbomify.com/CVE-2020-13976/): Command injection in n/a (high 8.8)
- [CVE-2012-6297](https://insights.sbomify.com/CVE-2012-6297/): Command injection in n/a (high 8.8)
- [CVE-2009-2765](https://insights.sbomify.com/CVE-2009-2765/): Command injection in n/a (high 8.3)
- [CVE-2009-2766](https://insights.sbomify.com/CVE-2009-2766/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-6974 is a medium-severity vulnerability in n/a, published on 14 Aug 2009. An attacker needs administrator access to exploit it, 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-6974 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-6974/ (Markdown: https://insights.sbomify.com/CVE-2008-6974/index.md)
```

## Sources

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

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