# CVE-2009-2256: Denial of service in n/a

> Remote attackers can cause a denial of service on Netgear DG632 routers by sending a specific HTTP POST request to the administrative interface.

- **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:** 30 Jun 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2fvw-3vhp-2m2r

## What is CVE-2009-2256?

CVE-2009-2256 is a high-severity denial of service vulnerability in n/a, published on 30 Jun 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The administrative web interface on the Netgear DG632 with firmware 3.4.0_ap allows remote attackers to cause a denial of service (web outage) via an HTTP POST request to cgi-bin/firmwarecfg.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Netgear Dg632.

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

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

## Is CVE-2009-2256 being exploited?

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

Public exploit code:

- Netgear DG632 Router - Remote Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-2257](https://insights.sbomify.com/CVE-2009-2257/): Auth bypass in n/a (high 7.8)
- [CVE-2009-2258](https://insights.sbomify.com/CVE-2009-2258/): Path traversal in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2256 is a high-severity denial of service vulnerability in n/a, published on 30 Jun 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-2256 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-2256/ (Markdown: https://insights.sbomify.com/CVE-2009-2256/index.md)
```

## Sources

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

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