# CVE-2009-0680: Path traversal in n/a

> Remote attackers can crash the Netgear SSL312 device via crafted query strings in the web interface, causing denial of service.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:N/I:N/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7ghv-3prv-p3qv

## What is CVE-2009-0680?

CVE-2009-0680 is a high-severity path traversal vulnerability in n/a, published on 22 Feb 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

cgi-bin/welcome/VPN_only in the web interface in Netgear SSL312 allows remote attackers to cause a denial of service (device crash) via a crafted query string, as demonstrated using directory traversal sequences.

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

## Which versions are affected by CVE-2009-0680?

It affects 1 product.


Products: Netgear Ssl312.

## How do I fix CVE-2009-0680?

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

## Is CVE-2009-0680 being exploited?

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

Public exploit code:

- Netgear SSL312 Router - Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-5562](https://insights.sbomify.com/CVE-2007-5562/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-0680 and fix it if it is affected.

What it is: CVE-2009-0680 is a high-severity path traversal vulnerability in n/a, published on 22 Feb 2009. 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-2009-0680 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-2009-0680/ (Markdown: https://insights.sbomify.com/CVE-2009-0680/index.md)
```

## Sources

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

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