# CVE-2006-6059: Buffer overflow in MA521nd5.SYS driver 5.148.724.2003 for NetGear MA521 PCMCIA adapter allows remote attackers to execute arbitrary code via


- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 22 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m2q2-p8vg-r5cw

## What is CVE-2006-6059?

CVE-2006-6059 is a critical vulnerability in n/a, published on 22 Nov 2006. 

### Official description

Buffer overflow in MA521nd5.SYS driver 5.148.724.2003 for NetGear MA521 PCMCIA adapter allows remote attackers to execute arbitrary code via (1) beacon or (2) probe 802.11 frame responses with an long supported rates information element.  NOTE: this issue was reported as a "memory corruption" error, but the associated exploit code suggests that it is a buffer overflow.

## Which versions are affected by CVE-2006-6059?

It affects 1 product.


Products: Netgear Ma521 Driver.

## How do I fix CVE-2006-6059?

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

## Is CVE-2006-6059 being exploited?

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

Public exploit code:

- Netgear MA521 Wireless Driver 5.148.724 - 'Beacon Probe' Remote Buffer Overflow (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-6059 and fix it if it is affected.

What it is: CVE-2006-6059 is a critical vulnerability in n/a, published on 22 Nov 2006. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-6059 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-2006-6059/ (Markdown: https://insights.sbomify.com/CVE-2006-6059/index.md)
```

## Sources

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

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