dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 20 Apr 2023.
Internet ExplorerApplication · Microsoft

CVE-2013-3163

HIGH · 8.8 CVSS v3.1 Published 2013-07-10
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 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 through 10 allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site, aka "Internet Explorer Memory Corruption Vulnerability," a different vulnerability than CVE-2013-3144 and CVE-2013-3151.

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

Memory corruption vulnerability in Internet Explorer 8-10 allowing remote code execution or denial of service via crafted websites. Exploitable through malicious web pages targeting the browser's rendering engine.

MitigationApply Microsoft security update MS13-037 (or subsequent cumulative update) to patch the vulnerability, or upgrade to a supported Internet Explorer version or alternative browser.

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= 9= 10

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 Internet Explorer, click the gear icon or Help menu, select 'About Internet Explorer' to view the version number, or check the registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Internet Explorer\Version
    Affected if The version shown is 8.x, 9.x, or 10.x (these are the affected versions)
  2. Verify whether IE is actively used
    Check if Internet Explorer is set as the default browser or is commonly accessed in the environment. Review browser usage or default program associations in Windows Control Panel
    Affected if Internet Explorer 8, 9, or 10 is used as a primary or default browser
  3. Confirm patch status
    Open Windows Update history or check Add/Remove Programs for installed security updates. Look for security update KB2846071 (from MS13-059) or any subsequent Internet Explorer cumulative security updates
    Affected if The relevant security update is not installed and the system still runs unpatched IE 8, 9, or 10

User is affected if Internet Explorer versions 8, 9, or 10 is installed and used without the MS13-059 or subsequent cumulative security updates applied

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
Vendor patch docs.microsoft.com →
Interim mitigation

Apply Microsoft security update MS13-037 (or subsequent cumulative update) to patch the vulnerability, or upgrade to a supported Internet Explorer version or alternative browser.

Recommended fix High confidence

Internet Explorer 11 (or Microsoft Edge on Windows 10+)

  1. Upgrade Internet Explorer to version 11, which is the first unaffected version for this vulnerability
  2. For Windows 7 systems: Install Internet Explorer 11 via Windows Update or download from Microsoft Update Catalog
  3. For Windows 8.1 systems: IE 11 is included by default; ensure Windows Updates are applied
  4. For Windows 10 systems: Use Microsoft Edge (the successor to IE) instead of Internet Explorer
  5. Apply all subsequent cumulative security updates for Internet Explorer 11 after the upgrade
  6. Alternatively, migrate to Microsoft Edge or another modern browser (Chrome, Firefox) as Internet Explorer is deprecated
Caveat IE 11 may have compatibility issues with older intranet applications or legacy web apps; test critical business applications before deployment. Some enterprise-specific features and ActiveX controls may not function identically.

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
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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