CVE-2009-0282
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInteger 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceInteger overflow (possibly signedness error) in Ralink USB wireless adapter drivers (RT73, rt2400, rt2500, rt2570, rt61) allows remote attackers to cause denial of service and potentially execute arbitrary code via a Probe Request packet containing an excessively long SSID field.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.08CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Ralink wireless adapter hardwareUse system hardware inventory tools (lspci, lsusb, or Windows Device Manager) to list USB and PCI wireless adapters. Look for Ralink Technology or RT2x00 series devices.Affected if A Ralink USB wireless adapter with model RT73, rt2400, rt2500, rt2570, or rt61 is present in the system hardware list
-
Locate the driver for the Ralink adapterCheck the installed wireless driver package. On Linux, examine kernel modules (lsmod, modinfo). On Windows, check Device Manager driver properties. Identify the driver file name and package providing wireless functionality.Affected if The driver package name or module name corresponds to one of the affected drivers (rt73, rt2400, rt2500, rt2570, rt61)
-
Retrieve the driver versionQuery the installed driver version through the operating system driver management interface, or read driver file properties. For Linux rt2x00 drivers, check /proc/version or use modinfo on the relevant module.Affected if The displayed driver version matches 3.08, or falls within the affected version range for the specific driver model
-
Verify network stack accepts Probe Request packetsConfirm the wireless interface is active and the driver has processing enabled for 802.11 probe request frames. This is typically the default operational state for an active wireless adapter.Affected if The wireless adapter interface is up and the driver is actively processing incoming probe request frames (default operational mode)
The system is affected if it has a Ralink USB wireless adapter (RT73, rt2400, rt2500, rt2570, or rt61) running driver version 3.08 (for Rt73) with an active wireless interface processing probe requests.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate affected wireless adapter drivers to vendor-patched versions; if patches are unavailable for legacy hardware, replace with newer adapters that receive security updates.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2009-0282 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-0282 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data