# CVE-2006-4982: Auth bypass in n/a

> Attackers can bypass network access controls by spoofing MAC addresses of devices on the exception list, requiring physical proximity.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **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:** 26 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9qgh-fw7f-c6jp

## What is CVE-2006-4982?

CVE-2006-4982 is a medium-severity authentication bypass vulnerability in n/a, published on 26 Sep 2006. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cisco NAC maintains an exception list that does not record device properties other than MAC address, which allows physically proximate attackers to bypass control methods and join a local network by spoofing the MAC address of a different type of device, as demonstrated by using the MAC address of a disconnected printer.

## Which versions are affected by CVE-2006-4982?

It affects 1 product.


Products: Cisco Network Access Control.

## How do I fix CVE-2006-4982?

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

## Is CVE-2006-4982 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-4983](https://insights.sbomify.com/CVE-2006-4983/): Security feature bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-4982 and fix it if it is affected.

What it is: CVE-2006-4982 is a medium-severity authentication bypass vulnerability in n/a, published on 26 Sep 2006. 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-2006-4982 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-2006-4982/ (Markdown: https://insights.sbomify.com/CVE-2006-4982/index.md)
```

## Sources

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

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