# CVE-2006-4430: Security feature bypass in n/a

> Remote attackers can bypass Cisco NAC protection mechanisms by modifying HTTP headers or TCP/IP stack behavior, preventing agent installation.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xhqj-9p6p-qgxw

## What is CVE-2006-4430?

CVE-2006-4430 is a medium-severity vulnerability in n/a, published on 29 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Cisco Network Admission Control (NAC) 3.6.4.1 and earlier allows remote attackers to prevent installation of the Cisco Clean Access (CCA) Agent and bypass local and remote protection mechanisms by modifying (1) the HTTP User-Agent header or (2) the behavior of the TCP/IP stack.  NOTE: the vendor has disputed the severity of this issue, stating that users cannot bypass authentication mechanisms.

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

It affects 2 products.


Products: Cisco Network Admission Control, Cisco Network Admission Control Manager and Server System Software.

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

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

## Is CVE-2006-4430 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-1155](https://insights.sbomify.com/CVE-2008-1155/): Information disclosure in n/a (critical 10.0)
- [CVE-2013-1124](https://insights.sbomify.com/CVE-2013-1124/): Security feature bypass in n/a (medium 5.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4430 is a medium-severity vulnerability in n/a, published on 29 Aug 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2006-4430 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-4430/ (Markdown: https://insights.sbomify.com/CVE-2006-4430/index.md)
```

## Sources

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

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