CVE-2012-1889

Exp

Microsoft XML Core Services 3.0, 4.0, 5.0, and 6.0 accesses uninitialized memory locations, which allows remote attackers to execute arbitrary code or cause a denial of service (memory corruption) via a crafted web site.

Published: 2012-06-13 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2012-1889 is rated Critical Active Threat (95.2/100): CVSS High severity, with high exploitation likelihood (EPSS 83.64%, 100th percentile). CISA KEV confirms active exploitation (added 2022-06-08) affecting Microsoft / XML Core Services. a weakness (CWE-787) Unauthenticated remote administrative access may be possible. The CISA remediation deadline has passed—treat as an emergency patch priority.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

CISA KEV Record for CVE-2012-1889

Name: Microsoft XML Core Services Memory Corruption Vulnerability · CISA KEV detail

Exploit added: 2022-06-08

Action due: 2022-06-22

Required action: Apply updates per vendor instructions.

Public exploit references (Exploit-DB) for CVE-2012-1889

EDB-ID Source Kind Published Link
19186 exploit_db edb 2012-06-16 Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2012-1889

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-16 83.52% 83.64% +0.12%
2 2026-06-15 93.12% 83.52% -9.60%
3 2026-04-07 — 93.12% —

Full EPSS history (30 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2012-1889

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:R)
A real person has to do something—click, install, enable—otherwise it doesn’t land.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0
9.3 2.0 HIGH
AV:N/AC:M/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 8.6 10.0 [email protected]

Weakness enumeration for CVE-2012-1889

Affected software / configurations for CVE-2012-1889

Vendor Product Version Raw CPE
microsoft xml_core_services 3.0 cpe:2.3:a:microsoft:xml_core_services:3.0:*:*:*:*:*:*:*
microsoft xml_core_services 4.0 cpe:2.3:a:microsoft:xml_core_services:4.0:*:*:*:*:*:*:*
microsoft xml_core_services 6.0 cpe:2.3:a:microsoft:xml_core_services:6.0:*:*:*:*:*:*:*
microsoft xml_core_services 5.0 cpe:2.3:a:microsoft:xml_core_services:5.0:*:*:*:*:*:*:*

References for CVE-2012-1889

cvelogic Threat Intelligence