dbcve.org
Xml Core ServicesApplication · Microsoft

CVE-2013-0006

HIGH · 8.8 CVSS v3.1 Published 2013-01-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 XML Core Services (aka MSXML) 3.0, 5.0, and 6.0 does not properly parse XML content, which allows remote attackers to execute arbitrary code via a crafted web page, aka "MSXML Integer Truncation 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 confidence

This is an integer truncation vulnerability in Microsoft XML Core Services (MSXML) versions 3.0, 5.0, and 6.0 that allows remote code execution. The vulnerability occurs when MSXML improperly parses crafted XML content, enabling attackers to execute arbitrary code via malicious web pages.

MitigationApply Microsoft's security update for this vulnerability. Additionally, configure browsers to disable active scripting and restrict access to untrusted websites to reduce attack surface.

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
Xml Core ServicesApplication
Affected:= 3.0= 4.0= 6.0= 5.0
Windows 7Operating system
Affected:all versions
Windows 8Operating system
Affected:all versions
Windows Server 2003Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions
Windows VistaOperating system
Affected:all versions
Windows XpOperating system
Affected:all versions

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. Verify MSXML installation
    Check for the presence of MSXML DLL files in system directories. Common paths: %SystemRoot%\System32\msxml3.dll, msxml4.dll, msxml5.dll, msxml6.dll. Use PowerShell command: Get-ChildItem -Path $env:SystemRoot\System32 -Filter 'msxml*.dll' | Select-Object Name, VersionInfo
    Affected if Any MSXML DLL (version 3.0, 4.0, 5.0, or 6.0) is present on the system
  2. Determine installed MSXML version
    Query the exact version of each MSXML DLL found. In PowerShell: (Get-Item 'C:\Windows\System32\msxml6.dll').VersionInfo.FileVersion. Check msxml3.dll, msxml4.dll, msxml5.dll, and msxml6.dll individually
    Affected if The installed version is 3.0.x, 4.0.x, 5.0.x, or 6.0.x (all versions within these major releases are affected)
  3. Identify applications using MSXML
    Review application usage of MSXML parsers. Check registry keys under HKLM\SOFTWARE\Classes\TypeLib\{F5078F18-C551-11D3-89B9-0000F81FE221} for MSXML versions registered, or examine application logs and dependencies for msxml*.dll load events
    Affected if Any application or service that leverages MSXML for XML parsing is present and active
  4. Check browser Active Scripting status
    In Internet Explorer, go to Internet Options > Security > Custom Level > Script ActiveX controls marked safe for scripting. For other browsers, check if they use MSXML via COM automation. This vulnerability is exploitable through malicious web pages
    Affected if Browser Active Scripting is enabled and the system processes untrusted XML content
  5. Verify Windows version and MSXML presence
    Run 'winver' or 'systeminfo' to confirm Windows version. Cross-reference with affected list: Windows XP, Vista, 7, 8, Server 2003, 2008, 2008 R2, 2012. Then check if MSXML DLLs exist on that system
    Affected if Running any of the listed Windows versions AND MSXML is installed

A system is affected if it runs any Windows version from XP to Server 2012 and has MSXML version 3.0, 4.0, 5.0, or 6.0 installed, especially if browsers or applications process XML content.

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

Apply Microsoft's security update for this vulnerability. Additionally, configure browsers to disable active scripting and restrict access to untrusted websites to reduce attack surface.

Fix this in Xml Core Services Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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