# CVE-2006-5745: Memory corruption in n/a

> Remote attackers can execute arbitrary code via memory corruption in the XMLHTTP ActiveX control when accessed through Internet Explorer.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 6 Nov 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-x5x2-7mmp-555x

## What is CVE-2006-5745?

CVE-2006-5745 is a high-severity memory corruption vulnerability in n/a, published on 6 Nov 2006. 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

Unspecified vulnerability in the setRequestHeader method in the XMLHTTP (XML HTTP) ActiveX Control 4.0 in Microsoft XML Core Services 4.0 on Windows, when accessed by Internet Explorer, allows remote attackers to execute arbitrary code via crafted arguments that lead to memory corruption, a different vulnerability than CVE-2006-4685.  NOTE: some of these details are obtained from third party information.

## Which versions are affected by CVE-2006-5745?

It affects 1 product.


Products: Microsoft Xml Core Services.

## How do I fix CVE-2006-5745?

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

## Is CVE-2006-5745 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-5745 exists.

Public exploit code:

- MS06-071 Microsoft Internet Explorer XML Core Services HTTP Request Handling (metasploit)
- Microsoft Internet Explorer 6/7 - XML Core Services Remote Code Execution (1) (exploitdb)
- Microsoft Internet Explorer 6/7 - XML Core Services Remote Code Execution (2) (exploitdb)
- Microsoft Internet Explorer 6/7 - XML Core Services Remote Code Execution (3) (exploitdb)
- Microsoft Internet Explorer - XML Core Services HTTP Request Handling (MS06-071) (Metasploit) (exploitdb)

## 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-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-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-2006-5745 and fix it if it is affected.

What it is: CVE-2006-5745 is a high-severity memory corruption vulnerability in n/a, published on 6 Nov 2006. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-5745 exists.

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

## Sources

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

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