# 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


- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Apr 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7r55-xf64-gwj6

## What is CVE-2016-0147?

CVE-2016-0147 is a high-severity vulnerability in n/a, published on 12 Apr 2016. 

### Official description

Microsoft XML Core Services 3.0 allows remote attackers to execute arbitrary code via a crafted web site, aka "MSXML 3.0 Remote Code Execution Vulnerability."

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2016-0147?

It affects 1 product.


Products: Microsoft Xml Core Services.

## How do I fix CVE-2016-0147?

No fix has been published for CVE-2016-0147 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-0147 being exploited?

There is no known exploitation of CVE-2016-0147 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2012-1889](https://insights.sbomify.com/CVE-2012-1889/): Microsoft XML Core Services Memory Corruption (high 8.8, exploited in the wild)
- [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-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-2016-0147 and fix it if it is affected.

What it is: CVE-2016-0147 is a high-severity vulnerability in n/a, published on 12 Apr 2016. 
Exploitation: There is no known exploitation of CVE-2016-0147 in the wild and no public exploit code.

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-2016-0147/ (Markdown: https://insights.sbomify.com/CVE-2016-0147/index.md)
```

## Sources

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

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