# CVE-2009-3092: Memory corruption in n/a

> A buffer overflow vulnerability in the ASUS WL-500W wireless router allows remote attackers to potentially execute arbitrary code or cause denial of service.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4mxh-q2pf-wp5x

## What is CVE-2009-3092?

CVE-2009-3092 is a critical memory corruption vulnerability in n/a, published on 8 Sep 2009. It can be exploited over the network, with no action from the victim.

### Official description

Buffer overflow on the ASUS WL-500W wireless router has unknown impact and remote attack vectors, as demonstrated by a certain module in VulnDisco Pack Professional 8.11.  NOTE: as of 20090903, this disclosure has no actionable information. However, because the VulnDisco Pack author is a reliable researcher, the issue is being assigned a CVE identifier for tracking purposes.

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

It affects 1 product.


Products: Asus Asus Wl-500w.

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

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

## Is CVE-2009-3092 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-3093](https://insights.sbomify.com/CVE-2009-3093/): Other in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-3092 is a critical memory corruption vulnerability in n/a, published on 8 Sep 2009. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-3092 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-2009-3092/ (Markdown: https://insights.sbomify.com/CVE-2009-3092/index.md)
```

## Sources

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

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