IeApplication · Microsoft

CVE-2006-4777

HIGH · 7.6 CVSS v2.0 Published 2006-09-14

Mitigation only

No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.

See remediation →

85/100

Remediation priority · High

High EPSS Remotely reachable No privileges Zero-click

Official description

NVD · unedited

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.

Technical summary

dbcve analysis · moderate confidence

Heap-based buffer overflow in the DirectAnimation.PathControl COM object (daxctle.ocx) in Internet Explorer 6.0 SP1 allows remote code execution via specially crafted arguments to the KeyFrame method, likely exploiting an integer overflow condition.

MitigationDisable the vulnerable DirectAnimation COM component via registry or upgrade from Internet Explorer 6.0 SP1 to a supported browser version; apply any available Microsoft patches for this component.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions

NVD · CPE data

IeApplication

Affected:= 6.0

CVSS breakdown

From the vector

Attack vector: Network
Complexity: High
Authentication: None
Confidentiality: Complete
Integrity: Complete
Availability: Complete

AV:N/AC:H/Au:N/C:C/I:C/A:C

Am I affected?

dbcve checks

Work through these to decide whether this CVE applies to you.

Check Internet Explorer version

Open IE, go to Help > About Internet Explorer. Verify the version is exactly 6.0 and Service Pack 1 is installed.

Affected if The installed IE version is 6.0 SP1 - other versions (later or earlier) are not affected by this specific CVE.
Locate the DirectAnimation component file

Search for daxctle.ocx on the system. Common paths include C:\Windows\System32\ and C:\Program Files\Internet Explorer\. Use: dir /s C:\daxctle.ocx

Affected if The file daxctle.ocx exists on the system, indicating the DirectAnimation COM component is present.
Verify DirectAnimation COM object registration

Check Windows Registry for the DirectAnimation.PathControl CLSID. Look in HKEY_CLASSES_ROOT\DirectAnimation.PathControl or use: reg query "HKCR\DirectAnimation.PathControl"

Affected if The COM object is registered in the registry, meaning it can be instantiated by IE.
Check if ActiveX control is enabled in IE

In IE, go to Tools > Internet Options > Security > Custom Level. Look for 'Run ActiveX controls and plugins' and 'Script ActiveX controls marked safe for scripting' settings.

Affected if ActiveX controls are enabled or set to Prompt for the relevant security zone (Internet/Local Intranet), allowing the vulnerable component to execute.
Confirm vulnerability trigger condition

The vulnerability requires the KeyFrame method of the DirectAnimation.PathControl object to be called with maliciously crafted arguments. This typically occurs when visiting a malicious webpage that instantiates the control and calls the method.

Affected if A user with IE 6.0 SP1, the DirectAnimation component present, and ActiveX enabled visits a webpage that exploits the KeyFrame method.

A user is affected if they have Internet Explorer 6.0 SP1 with the DirectAnimation.PathControl COM component (daxctle.ocx) present and ActiveX controls enabled, making the KeyFrame method accessible to web pages.

Generated from the published advisory. Verify against your own configuration.

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Disable the vulnerable DirectAnimation COM component via registry or upgrade from Internet Explorer 6.0 SP1 to a supported browser version; apply any available Microsoft patches for this component.

Fix this in Ie Scoped from the published advisory

Consultation2.0 h
Implementation2.0 h
Testing2.0 h
Review / QA1.0 h

7.0 hours of engineering $1,240

Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2006-4777 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2006-4777 in production — separate from our analysis above.

Notes0 Guidelines

Know something about CVE-2006-4777?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here

Verified mitigations, workarounds, and config changes
Version or environment caveats, and links to real fixes
No weaponised exploit code, or anything meant to cause harm
No spam, self-promotion, credentials, or personal data

At a glance

A fix existsA vendor remedy is published

Severity 7.6 High

Exploit likelihood EPSS, next 30 days 79.8%

Affects: Ie

Remediation

A high-priority fix

Fix this in Ie 7 hrs · Low

Typical engagement from $1,240

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2006-4777 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

Check your environment

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

Scan for this in your stack

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References