CVE-2010-0806
Microsoft Internet Explorer Use-After-Free Vulnerability
Description
Use-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."
Description as published by the source, in English.
Key facts
- Published
- 2010-03-10
- Last modified
- 2026-06-16
- Assigned by
- secure@microsoft.com
- CVSS vector
AV:N/AC:M/Au:N/C:C/I:C/A:C- Scored by
- nvd@nist.gov (NVD Primary)
- Probability of exploitation
-
82.2 %
among the highest of all known vulnerabilities
EPSS, next 30 days, model v2026.06.15 - Fix available
- Yes, see references
Actively exploited
CISA added this vulnerability to the Known Exploited Vulnerabilities catalogue on 2026-05-20, with a remediation deadline of 2026-06-03 for US federal agencies.
Required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Affected products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| Microsoft | Internet Explorer | 5.01 | Affected |
| Microsoft | Internet Explorer | 6 | Affected |
| Microsoft | Internet Explorer | 7 | Affected |
| Microsoft | Internet Explorer | 8 | Affected |
| Microsoft | Windows 2000 | all versions listed | Not affected |
| Microsoft | Windows 7 | all versions listed | Not affected |
| Microsoft | Windows Server 2003 | all versions listed | Not affected |
| Microsoft | Windows Server 2008 | all versions listed | Not affected |
| Microsoft | Windows Server 2008 | r2 | Not affected |
| Microsoft | Windows Vista | all versions listed | Not affected |
| Microsoft | Windows Xp | all versions listed | Not affected |
Weakness type
- CWE-399
-
CWE-416: Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within…
References
- http://blogs.technet.com/msrc/archive/2010/03/09/security-advisory-981374-released.aspx
- http://osvdb.org/62810
- http://secunia.com/advisories/38860
- http://www.kb.cert.org/vuls/id/744549
- http://www.microsoft.com/technet/security/advisory/981374.mspx
- http://www.securityfocus.com/bid/38615
- http://www.us-cert.gov/cas/techalerts/TA10-068A.html
- http://www.us-cert.gov/cas/techalerts/TA10-089A.html
- http://www.vupen.com/english/advisories/2010/0567
- http://www.vupen.com/english/advisories/2010/0744
- https://docs.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-018
- https://exchange.xforce.ibmcloud.com/vulnerabilities/56772
- https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A84…
- http://blogs.technet.com/msrc/archive/2010/03/09/security-advisory-981374-released.aspx
- http://osvdb.org/62810
- http://secunia.com/advisories/38860
- http://www.kb.cert.org/vuls/id/744549
- http://www.microsoft.com/technet/security/advisory/981374.mspx
- http://www.securityfocus.com/bid/38615
- http://www.us-cert.gov/cas/techalerts/TA10-068A.html
Does this affect you?
A vulnerability matters only if you run the product, in an affected version, somewhere an attacker can reach.