# CVE-2004-0459: The Clear Channel Assessment (CCA) algorithm in the IEEE 802.11 wireless protocol, when using DSSS transmission encoding, allows remote atta


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 May 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-349j-652r-ghg9

## What is CVE-2004-0459?

CVE-2004-0459 is a medium-severity vulnerability in n/a, published on 20 May 2004. 

### Official description

The Clear Channel Assessment (CCA) algorithm in the IEEE 802.11 wireless protocol, when using DSSS transmission encoding, allows remote attackers to cause a denial of service via a certain RF signal that causes a channel to appear busy (aka "jabber"), which prevents devices from transmitting data.

## Which versions are affected by CVE-2004-0459?

It affects 1 product.


Products: Ieee 802.11 Wireless Protocol.

## How do I fix CVE-2004-0459?

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

## Is CVE-2004-0459 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0459 and fix it if it is affected.

What it is: CVE-2004-0459 is a medium-severity vulnerability in n/a, published on 20 May 2004. 
Exploitation: There is no known exploitation of CVE-2004-0459 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-2004-0459/ (Markdown: https://insights.sbomify.com/CVE-2004-0459/index.md)
```

## Sources

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

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