# CVE-2005-3482: Security feature bypass in n/a

> Remote attackers can bypass wireless security to send unencrypted traffic to a secure network by spoofing MAC addresses of authenticated hosts.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Nov 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7cgh-wxqr-fvg7

## What is CVE-2005-3482?

CVE-2005-3482 is a medium-severity vulnerability in n/a, published on 3 Nov 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cisco 1200, 1131, and 1240 series Access Points, when operating in Lightweight Access Point Protocol (LWAPP) mode and controlled by 2000 and 4400 series Airespace WLAN controllers running 3.1.59.24, allow remote attackers to send unencrypted traffic to a secure network using frames with the MAC address of an authenticated end host.

## Which versions are affected by CVE-2005-3482?

It affects 3 products.


Products: Cisco Aironet Ap1131, Cisco Aironet Ap1200, Cisco Aironet Ap1240.

## How do I fix CVE-2005-3482?

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

## Is CVE-2005-3482 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3482 and fix it if it is affected.

What it is: CVE-2005-3482 is a medium-severity vulnerability in n/a, published on 3 Nov 2005. 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-2005-3482 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-2005-3482/ (Markdown: https://insights.sbomify.com/CVE-2005-3482/index.md)
```

## Sources

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

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