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

> Remote attackers can execute arbitrary code or cause denial of service in Cisco CallManager via crafted packets triggering a buffer overflow in the aupair service.

- **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:** 12 Jul 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3643-vfjq-qr3j

## What is CVE-2005-2244?

CVE-2005-2244 is a medium-severity memory corruption vulnerability in n/a, published on 12 Jul 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The aupair service (aupair.exe) in Cisco CallManager (CCM) 3.2 and earlier, 3.3 before 3.3(5), 4.0 before 4.0(2a)SR2b, and 4.1 4.1 before 4.1(3)SR1 allows remote attackers to execute arbitrary code or corrupt memory via crafted packets that trigger a memory allocation failure and lead to a buffer overflow.

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

It affects 1 product.


Products: Cisco Call Manager.

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

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

## Is CVE-2005-2244 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2004-1760](https://insights.sbomify.com/CVE-2004-1760/): Auth bypass in n/a (critical 10.0)
- [CVE-2007-4634](https://insights.sbomify.com/CVE-2007-4634/): SQL injection in n/a (critical 9.3)
- [CVE-2006-0368](https://insights.sbomify.com/CVE-2006-0368/): Denial of service in n/a (high 7.8)
- [CVE-2006-0367](https://insights.sbomify.com/CVE-2006-0367/): Privilege escalation in n/a (medium 6.5)
- [CVE-2007-5468](https://insights.sbomify.com/CVE-2007-5468/): Auth bypass in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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