# CVE-2009-0282: Integer overflow in n/a

> Remote attackers can cause a crash or execute arbitrary code via a crafted Probe Request packet exploiting an integer overflow in Ralink wireless drivers.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** DSA-1712-1, DSA-1713-1, DSA-1714-1, GHSA-7q9j-2fg6-cx58

## What is CVE-2009-0282?

CVE-2009-0282 is a critical vulnerability in n/a, published on 27 Jan 2009. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer overflow in Ralink Technology USB wireless adapter (RT73) 3.08 for Windows, and other wireless card drivers including rt2400, rt2500, rt2570, and rt61, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a Probe Request packet with a long SSID, possibly related to an integer signedness error.

Weakness: CWE-189

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

It affects 1 product.


Products: Ralinktech Rt73.

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

Apply the vendor's patch.

## Is CVE-2009-0282 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2009-0282 is a critical vulnerability in n/a, published on 27 Jan 2009. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-0282 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-0282/ (Markdown: https://insights.sbomify.com/CVE-2009-0282/index.md)
```

## Sources

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

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