# CVE-2006-2322: Misconfiguration in n/a

> Remote attackers can proxy arbitrary TCP connections due to a default transparent proxy configuration in Cisco AVS devices.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/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:** 12 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gv2j-9x52-524g

## What is CVE-2006-2322?

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

### Official description

The transparent proxy feature of the Cisco Application Velocity System (AVS) 3110 5.0 and 4.0 and earlier, and 3120 5.0.0 and earlier, has a default configuration that allows remote attackers to proxy arbitrary TCP connections, aka Bug ID CSCsd32143.

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

It affects 2 products.


Products: Cisco Application Velocity System 3110, Cisco Application Velocity System 3120.

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

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

## Is CVE-2006-2322 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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