# CVE-2010-2307: Path traversal in n/a

> Remote attackers can read arbitrary files on Motorola SURFBoard cable modems via directory traversal in URL requests.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jun 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p74c-gqrv-v859

## What is CVE-2010-2307?

CVE-2010-2307 is a medium-severity path traversal vulnerability in n/a, published on 16 Jun 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple directory traversal vulnerabilities in the web server for Motorola SURFBoard cable modem SBV6120E running firmware SBV6X2X-1.0.0.5-SCM-02-SHPC allow remote attackers to read arbitrary files via (1) "//" (multiple leading slash), (2) ../ (dot dot) sequences, and encoded dot dot sequences in a URL request.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2010-2307?

It affects 1 product.


Products: Motorola Surfboard Sbv6120e.

## How do I fix CVE-2010-2307?

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

## Is CVE-2010-2307 being exploited?

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

Public exploit code:

- Motorola Surfboard Cable Modem - Directory Traversal (exploitdb)
- Motorola SBV6120E SURFboard Digital Voice Modem SBV6X2X-1.0.0.5-SCM - Directory Traversal (nuclei): http/cves/2010/CVE-2010-2307.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2307 and fix it if it is affected.

What it is: CVE-2010-2307 is a medium-severity path traversal vulnerability in n/a, published on 16 Jun 2010. 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-2010-2307 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-2010-2307/ (Markdown: https://insights.sbomify.com/CVE-2010-2307/index.md)
```

## Sources

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

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