IeApplication · Microsoft

CVE-2006-5884

HIGH · 7.5 CVSS v2.0 Published 2006-11-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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.

NVD · unedited
Multiple unspecified vulnerabilities in DirectAnimation ActiveX controls for Microsoft Internet Explorer 5.01 through 6 have unknown impact and remote attack vectors, possibly related to (1) Danim.dll and (2) Lmrt.dll, a different set of vulnerabilities than CVE-2006-4446 and CVE-2006-4777.

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.

dbcve analysis · moderate confidence

Multiple vulnerabilities exist in DirectAnimation ActiveX controls for Internet Explorer 5.01 through 6, affecting Danim.dll and Lmrt.dll libraries. These unspecified vulnerabilities have unknown impact and can be exploited remotely via the vulnerable ActiveX controls.

MitigationDisable or remove DirectAnimation ActiveX controls in Internet Explorer, or migrate to a supported browser as IE 6 and earlier are no longer supported.

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

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.

NVD · CPE data
IeApplication
Affected:= 6
Internet ExplorerApplication
Affected:= 5.1= 5.5

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.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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.

dbcve checks

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

  1. Check Internet Explorer version
    Open Internet Explorer, click Help > About Internet Explorer, or run 'winver' command from Run dialog
    Affected if Version is 5.1, 5.5, or 6.0
  2. Locate Danim.dll on the system
    Search for Danim.dll in system directories (C:\Windows\System32\) or use 'dir /s C:\Danim.dll' from command prompt
    Affected if File exists on the system (indicates DirectAnimation component is present)
  3. Locate Lmrt.dll on the system
    Search for Lmrt.dll in system directories or use 'dir /s C:\Lmrt.dll' from command prompt
    Affected if File exists on the system (indicates DirectAnimation component is present)
  4. Check if DirectAnimation ActiveX controls are registered
    Open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Code Store Database\DOM Distribution, or check HKCR\CLSID for entries containing 'DirectAnimation' or the Danim/Lmrt component CLSIDs
    Affected if DirectAnimation CLSID entries exist in the registry, meaning the ActiveX controls are registered and can be invoked by IE

A user is affected if they run Internet Explorer 5.1, 5.5, or 6.0 AND have the Danim.dll or Lmrt.dll DirectAnimation components present and registered as ActiveX controls on their system

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

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable or remove DirectAnimation ActiveX controls in Internet Explorer, or migrate to a supported browser as IE 6 and earlier are no longer supported.

Fix this in Ie Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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

Primary sources

Practitioner notes

Contributed

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

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