# CVE-2005-4466: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via a malformed SIP REGISTER request in Interaction SIP Proxy.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-m2jg-x6cx-w676

## What is CVE-2005-4466?

CVE-2005-4466 is a high-severity memory corruption vulnerability in n/a, published on 22 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap-based buffer overflow in the SIPParser function in i3sipmsg.dll in Interaction SIP Proxy before 3.0.011 allows remote attackers to cause a denial of service and possibly execute arbitrary code via a REGISTER request with a SPI version number that contains a large number of space or tab characters.

## Which versions are affected by CVE-2005-4466?

It affects 1 product.


Products: Interactive Intelligence Interaction Sip Proxy.

## How do I fix CVE-2005-4466?

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

## Is CVE-2005-4466 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4466 exists.

Public exploit code:

- Interaction SIP Proxy 3.0 - Remote Heap Corruption Denial of Service (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4466 and fix it if it is affected.

What it is: CVE-2005-4466 is a high-severity memory corruption vulnerability in n/a, published on 22 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-4466 exists.

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-2005-4466/ (Markdown: https://insights.sbomify.com/CVE-2005-4466/index.md)
```

## Sources

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

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