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

> Remote attackers can execute arbitrary code via a heap-based buffer overflow in the DirectAnimation Path Control ActiveX object in Internet Explorer.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Sep 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-h8xv-8m4r-fp4f

## What is CVE-2006-4777?

CVE-2006-4777 is a high-severity memory corruption vulnerability in Microsoft Ie, published on 14 Sep 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Heap-based buffer overflow in the DirectAnimation Path Control (DirectAnimation.PathControl) COM object (daxctle.ocx) for Internet Explorer 6.0 SP1, on Chinese and possibly other Windows distributions, allows remote attackers to execute arbitrary code via unknown manipulations in arguments to the KeyFrame method, possibly related to an integer overflow, as demonstrated by daxctle2, and a different vulnerability than CVE-2006-4446.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Microsoft Ie.

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

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

## Is CVE-2006-4777 being exploited?

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

Public exploit code:

- Microsoft Internet Explorer - COM Object Remote Heap Overflow (exploitdb)
- MS06-067 Microsoft Internet Explorer Daxctle.OCX KeyFrame Method Heap Buffer Overflow Vulnerability (metasploit)
- Microsoft Internet Explorer - Daxctle.OCX KeyFrame Method Heap Buffer Overflow (MS06-067) (Metasploit) (exploitdb)
- malware del lado del cliente de explotacion de vulnerabilidad de internet explorer 6.0 SP1 en windows xp SP2. No requiere de consentimiento por parte del usuario y no descarga ningun archivo (github_poc): https://github.com/Mario1234/js-driveby-download-CVE-2006-4777

## Other vulnerabilities in Microsoft Ie

- [CVE-2007-0217](https://insights.sbomify.com/CVE-2007-0217/): Memory corruption in n/a (critical 10.0)
- [CVE-2007-0219](https://insights.sbomify.com/CVE-2007-0219/): Code injection in n/a (critical 10.0)
- [CVE-2006-1186](https://insights.sbomify.com/CVE-2006-1186/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0985](https://insights.sbomify.com/CVE-2004-0985/): Code injection in n/a (critical 10.0)
- [CVE-2004-0216](https://insights.sbomify.com/CVE-2004-0216/): Integer overflow in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-4777 is a high-severity memory corruption vulnerability in Microsoft Ie, published on 14 Sep 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-4777 exists.

Affected product: Microsoft Ie. 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-4777/ (Markdown: https://insights.sbomify.com/CVE-2006-4777/index.md)
```

## Sources

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

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