# CVE-2006-4194: Other in n/a

> Remote attackers could potentially send arbitrary UDP packets to intranet devices via SIP fixup commands on Cisco PIX firewalls, though the vendor could not reproduce the issue.

- **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:** 17 Aug 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-ffgq-wx3w-58gq

## What is CVE-2006-4194?

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

### Official description

Unspecified vulnerability in Cisco PIX 500 Series Security Appliances allows remote attackers to send arbitrary UDP packets to intranet devices via unspecified vectors involving Session Initiation Protocol (SIP) fixup commands, a different issue than CVE-2006-4032.  NOTE: the vendor, after working with the researcher, has been unable to reproduce the issue

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

It affects 8 products.


Products: Cisco Pix Firewall 501, Cisco Pix Firewall 506, Cisco Pix Firewall 515, Cisco Pix Firewall 515e, Cisco Pix Firewall 520, Cisco Pix Firewall 525, Cisco Pix Firewall 535, Cisco Pix Firewall Software.

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

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

## Is CVE-2006-4194 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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