CVE-2012-1889
High 8.8KEV · exploitedPublic exploitFix status unknownMicrosoft XML Core Services Memory Corruption Vulnerability
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Among the highest-scored CVEs. A prediction, not evidence.
CISA remediation deadline
Passed 1613 days ago for U.S. federal agencies
Description
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.
Weakness: CWE-119
Patching and mitigation
- Patch status
- Unknown: no source documents a fix
- Mitigation
- None documented
- Vendor guidance
- docs.microsoft.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| Microsoft | XML Core Services | Not documented | Not documented | CISA KEV |
Timeline
Disclosure
CVE record published by microsoft
Source: CVE Program (opens in a new tab)
08 Jun 2022KEV
Added to the CISA Known Exploited Vulnerabilities catalog
Source: CISA KEV (opens in a new tab)
08 Jun 2022Exploitation
Exploitation confirmed by CISA KEV
Source: CISA KEV (opens in a new tab)
Vendor guidance and references
- MS12-043 (opens in a new tab)vendor-advisory, x_refsource_ms, x_transferred
- http://technet.microsoft.com/security/advisory/2719615 (opens in a new tab)x_refsource_confirm, x_transferred
- TA12-174A (opens in a new tab)third-party-advisory, x_refsource_cert, x_transferred
- TA12-192A (opens in a new tab)third-party-advisory, x_refsource_cert, x_transferred
- https://nvd.nist.gov/vuln/detail/CVE-2012-1889 (opens in a new tab)government
- oval:org.mitre.oval:def:15195 (opens in a new tab)signature, vdb-entry, x_refsource_oval, x_transferred
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2012-1889 (opens in a new tab)government-resource
Public exploit code
Exploit or proof-of-concept code is publicly available on Exploit-DB. Shown as a prioritization and defensive-testing signal — treat exploit code as hostile and run it only against systems you are authorized to test.