# CVE-2006-6055: Stack-based buffer overflow in A5AGU.SYS 1.0.1.41 for the D-Link DWL-G132 wireless adapter allows remote attackers to execute arbitrary code


- **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-f8w3-7f86-fvgw

## What is CVE-2006-6055?

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

### Official description

Stack-based buffer overflow in A5AGU.SYS 1.0.1.41 for the D-Link DWL-G132 wireless adapter allows remote attackers to execute arbitrary code via a 802.11 beacon request with a long Rates information element (IE).

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

It affects 1 product.


Products: D-Link Dwl-G132.

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

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

## Is CVE-2006-6055 being exploited?

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

Public exploit code:

- D-Link DWL-G132 - Wireless Driver Beacon Rates Overflow (Metasploit) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-6055 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-6055 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-6055/ (Markdown: https://insights.sbomify.com/CVE-2006-6055/index.md)
```

## Sources

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

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