# CVE-2009-2976: Information disclosure in n/a

> Remote attackers can sniff wireless networks to discover sensitive MAC addresses, IP addresses, and configuration details from Cisco Aironet Access Points.

- **Severity:** High 7.8 (`AV:N/AC:L/Au:N/C:C/I:N/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:** 27 Aug 2009
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-v58x-whgv-c2w3

## What is CVE-2009-2976?

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

### Official description

Cisco Aironet Lightweight Access Point (AP) devices send the contents of certain multicast data frames in cleartext, which allows remote attackers to discover Wireless LAN Controller MAC addresses and IP addresses, and AP configuration details, by sniffing the wireless network.

Weakness: CWE-310

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

It affects 2 products.


Products: Cisco Aironet Ap1100, Cisco Aironet Ap1200.

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

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

## Is CVE-2009-2976 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-2861](https://insights.sbomify.com/CVE-2009-2861/): Denial of service in n/a (high 7.3)
- [CVE-2006-0354](https://insights.sbomify.com/CVE-2006-0354/): Denial of service in n/a (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2976 is a high-severity vulnerability in n/a, published on 27 Aug 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-2976 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-2976/ (Markdown: https://insights.sbomify.com/CVE-2009-2976/index.md)
```

## Sources

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

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