Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 24 Mar 2022.
Internet ExplorerApplication · Microsoft

CVE-2013-1347

HIGH · 8.8 CVSS v3.1 Published 2013-05-05
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Patch available

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
Microsoft Internet Explorer 8 does not properly handle objects in memory, which allows remote attackers to execute arbitrary code by accessing an object that (1) was not properly allocated or (2) is deleted, as exploited in the wild in May 2013.

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 confidence

Internet Explorer 8 contains a memory corruption vulnerability in its handling of objects in memory. The browser fails to properly manage objects that were either not correctly allocated or have been deleted, allowing attackers to execute arbitrary code via specially crafted web content.

MitigationUpgrade Internet Explorer to a patched version or migrate to a supported browser; apply the relevant Microsoft security update if still running IE8 in legacy environments.

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
Internet ExplorerApplication
Affected:= 8

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
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 checks

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

  1. Identify installed Internet Explorer version
    Open IE8, click 'Help' in the menu bar, then select 'About Internet Explorer'. Alternatively, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer to find the Version string value.
    Affected if The version listed is exactly 8.x (for example, 8.0.7601.17514)
  2. Confirm the specific IE8 build number
    In the About Internet Explorer dialog, note the full version number displayed. IE8 was released in multiple builds between 2009 and 2011.
    Affected if The version begins with 8.0 (such as 8.0.6001, 8.0.7600, or 8.0.7601) confirming it is the IE8 release
  3. Verify this is the only Internet Explorer version present
    Check if IE8 is the maximum version installed. Some systems may have IE8 as the maximum while others may have IE9, IE10, or IE11 installed alongside or as upgrades.
    Affected if IE8 is the highest Internet Explorer version installed on the system (IE9+ are not present)
  4. Determine if the system has received Microsoft security updates
    Open Windows Update history or the installed updates list. Search for security updates related to MS13-037 or subsequent IE cumulative updates released after May 2013.
    Affected if No security updates addressing CTreePos use-after-free (MS13-037 or later IE cumulative updates) have been installed on the IE8 system

A system is affected if Internet Explorer version 8 is installed and running without the MS13-037 or later cumulative security updates that address this use-after-free vulnerability in CTreePos object handling.

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.

dbcve · scoped
Patch available Apply the vendor patch
Interim mitigation

Upgrade Internet Explorer to a patched version or migrate to a supported browser; apply the relevant Microsoft security update if still running IE8 in legacy environments.

Recommended fix High confidence

Internet Explorer 11 (for Windows 7 SP1/Server 2008 R2 SP1) or Microsoft Edge (for Windows 10/11)

  1. 1. Determine the operating system version running Internet Explorer 8 (e.g., Windows 7, Windows Server 2008 R2)
  2. 2. If the OS supports Internet Explorer 11 (Windows 7 requires SP1, Server 2008 R2 requires SP1), upgrade to IE11 via Windows Update or Microsoft Update Catalog
  3. 3. If the OS cannot support IE11, apply Microsoft security update MS13-037 (released June 2013) which addresses CVE-2013-1347
  4. 4. If the OS is Windows 7 or Server 2008 R2 and no longer under extended support, migrate to a modern browser such as Microsoft Edge or Google Chrome
  5. 5. Verify the browser version after upgrade: IE11 should show version 11.0.9600 in Help > About Internet Explorer
Caveat Internet Explorer 11 may not be compatible with legacy internal applications; some older ActiveX controls and enterprise line-of-business apps may require compatibility mode or alternative solutions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Internet Explorer Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-1347 — 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-2013-1347 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