# CVE-2006-5273: Memory corruption in n/a

> Remote attackers can execute arbitrary code on McAfee ePolicy Orchestrator and related agents via a crafted packet due to a heap-based buffer overflow.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **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 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cmcq-56r6-cxh7

## What is CVE-2006-5273?

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

### Official description

Heap-based buffer overflow in McAfee ePolicy Orchestrator 3.5 through 3.6.1, ProtectionPilot 1.1.1 and 1.5, and Common Management Agent (CMA) 3.5.5.438 through 3.6.0.453 allows remote attackers to execute arbitrary code via a crafted packet.

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

It affects 3 products.


Products: Mcafee Common Management Agent, Mcafee E-Business Server, Mcafee Protectionpilot.

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

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

## Is CVE-2006-5273 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-5274](https://insights.sbomify.com/CVE-2006-5274/): Integer overflow in n/a (high 7.6)
- [CVE-2006-5272](https://insights.sbomify.com/CVE-2006-5272/): Memory corruption in n/a (high 7.5)
- [CVE-2005-4505](https://insights.sbomify.com/CVE-2005-4505/): Privilege escalation in n/a (high 7.2)
- [CVE-2009-5115](https://insights.sbomify.com/CVE-2009-5115/): Path traversal in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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