# CVE-2012-1889: Microsoft XML Core Services Memory Corruption

> Remote attackers can execute arbitrary code or cause denial of service via crafted websites exploiting uninitialized memory access in Microsoft XML Core Services.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 8 Jun 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jun 2012
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-hv88-2gcv-6mjq

## What is CVE-2012-1889?

CVE-2012-1889 is a high-severity memory corruption vulnerability in n/a, published on 13 Jun 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2012-1889?

It affects 1 product.


Products: Microsoft Xml Core Services.

## How do I fix CVE-2012-1889?

No fix has been published for CVE-2012-1889 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 22 Jun 2022.

## Is CVE-2012-1889 being exploited?

Yes. Attackers have exploited CVE-2012-1889 in the wild since at least 8 Jun 2022.

Public exploit code:

- 这里保存着我学习CVE-2012-1889这个漏洞的利用所用到的文件 (github_poc): https://github.com/whu-enjoy/CVE-2012-1889
- https://github.com/l-iberty/cve-2012-1889 (github_poc): https://github.com/l-iberty/cve-2012-1889
- MS12-043 Microsoft XML Core Services MSXML Uninitialized Memory Corruption (metasploit)
- Microsoft XML Core Services - MSXML Uninitialized Memory Corruption (MS12-043) (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2010-2561](https://insights.sbomify.com/CVE-2010-2561/): Microsoft XML Core Services (aka MSXML) 3.0 does not properly handle HTTP responses, which allows remote attackers to execute arbitrary code (critical 9.3)
- [CVE-2007-2223](https://insights.sbomify.com/CVE-2007-2223/): Integer overflow in n/a (critical 9.3)
- [CVE-2016-0147](https://insights.sbomify.com/CVE-2016-0147/): Microsoft XML Core Services 3.0 allows remote attackers to execute arbitrary code via a crafted web site, aka "MSXML 3.0 Remote Code Executi (high 8.8)
- [CVE-2006-5745](https://insights.sbomify.com/CVE-2006-5745/): Memory corruption in n/a (high 7.6)
- [CVE-2006-4686](https://insights.sbomify.com/CVE-2006-4686/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-1889 and fix it if it is affected.

What it is: CVE-2012-1889 is a high-severity memory corruption vulnerability in n/a, published on 13 Jun 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2012-1889 in the wild since at least 8 Jun 2022.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-1889/ (Markdown: https://insights.sbomify.com/CVE-2012-1889/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-1889
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-1889
- OSV: https://osv.dev/vulnerability/CVE-2012-1889

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-1889/
Summaries are generated and may contain mistakes; the official description above is the record.