CVE-2010-0806
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 · uneditedUse-after-free vulnerability in the Peer Objects component (aka iepeers.dll) in Microsoft Internet Explorer 6, 6 SP1, and 7 allows remote attackers to execute arbitrary code via vectors involving access to an invalid pointer after the deletion of an object, as exploited in the wild in March 2010, aka "Uninitialized Memory Corruption Vulnerability."
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 · high confidenceUse-after-free vulnerability in iepeers.dll (Peer Objects) in Internet Explorer 6, 6 SP1, and 7 allows remote attackers to execute arbitrary code by accessing an invalid pointer after an object has been deleted. This was actively exploited in the wild in March 2010.
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= 5.01= 6= 8= 7CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Check Internet Explorer versionOpen Internet Explorer, click Help > About Internet Explorer, or run 'winver' command and look for IE version informationAffected if The version displayed is 5.01, 6.0, or 7.0 (any SP level)
-
Verify iepeers.dll existsCheck for the presence of iepeers.dll in the Windows system directory (typically C:\Windows\System32\iepeers.dll) using File Explorer or command: dir C:\Windows\System32\iepeers.dllAffected if The file iepeers.dll exists on the system (this is the vulnerable Peer Objects component)
-
Confirm Peer Objects ActiveX controlCheck if the Peer Objects ActiveX control is registered. Open registry editor and navigate to HKLM\SOFTWARE\Microsoft\Internet Explorer\Controls or look for CLSID {3C2EFA36-7B38-4CC6-BB85-9A3A2C3C6B84} in HKCR\CLSIDAffected if The Peer Objects ActiveX control is registered and enabled in Internet Explorer
If Internet Explorer version 5.01, 6.0, or 7.0 is installed AND iepeers.dll is present, the system is vulnerable to CVE-2010-0806.
Generated from the published advisory. Verify against your own configuration.
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.
dbcve · scopedApply Microsoft security update MS10-018 or upgrade to a newer Internet Explorer version. For systems unable to patch, disable ActiveX controls and enforce Enhanced Protected Mode as compensating controls.
Internet Explorer 8 or later (or apply MS10-018 security update to affected versions)
- Apply Microsoft Security Bulletin MS10-018 (Cumulative Security Update for Internet Explorer), which was released March 30, 2010 to address this vulnerability
- Download and install MS10-018 from the Microsoft Download Center or via Windows Update
- Alternatively, upgrade to Internet Explorer 8 or later, which includes the fix for this vulnerability
- After applying the update or upgrading, restart Internet Explorer and verify the version to confirm the patch was applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0806 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-0806 in production — separate from our analysis above.
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.
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.
- 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