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

> Remote attackers can force a Motorola Surfboard cable modem to reboot or reset via CSRF, requiring user interaction to trigger the malicious request.

- **Severity:** High 7.8 (`AV:N/AC:M/Au:N/C:N/I:P/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 28 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c6xr-3cp2-f7f7

## What is CVE-2008-2002?

CVE-2008-2002 is a high-severity vulnerability in n/a, published on 28 Apr 2008. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities on Motorola Surfboard with software SB5100-2.3.3.0-SCM00-NOSH allow remote attackers to (1) cause a denial of service (device reboot) via the "Restart Cable Modem" value in the BUTTON_INPUT parameter to configdata.html, and (2) cause a denial of service (hard reset) via the "Reset All Defaults" value in the BUTTON_INPUT parameter to configdata.html.

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

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

It affects 1 product.


Products: Motorola Surfboard.

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

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

## Is CVE-2008-2002 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5196](https://insights.sbomify.com/CVE-2006-5196/): Denial of service in n/a (high 7.8)
- [CVE-2002-1944](https://insights.sbomify.com/CVE-2002-1944/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2002 is a high-severity vulnerability in n/a, published on 28 Apr 2008. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-2002 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-2008-2002/ (Markdown: https://insights.sbomify.com/CVE-2008-2002/index.md)
```

## Sources

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

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