# CVE-2014-6352: Microsoft Windows Code Injection

> Remote attackers can execute arbitrary code via crafted OLE objects in Microsoft Windows, requiring immediate patching.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 25 Feb 2022 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 Oct 2014
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-hcj8-r3vf-4jr7

## What is CVE-2014-6352?

CVE-2014-6352 is a high-severity code injection vulnerability in Microsoft Windows 7, published on 22 Oct 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, and Windows RT Gold and 8.1 allow remote attackers to execute arbitrary code via a crafted OLE object, as exploited in the wild in October 2014 with a crafted PowerPoint document.

## Which versions are affected by CVE-2014-6352?

It affects 8 products.


Products: Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 8.1, Microsoft Windows Rt, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista.

## How do I fix CVE-2014-6352?

No fix has been published for CVE-2014-6352 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 25 Aug 2022.

## Is CVE-2014-6352 being exploited?

Yes. Attackers have exploited CVE-2014-6352 in the wild since at least 25 Feb 2022.

Public exploit code:

- Microsoft Windows - OLE Package Manager SandWorm (exploitdb)
- Microsoft Windows - OLE Package Manager Code Execution (MS14-060) (Metasploit) (exploitdb)
- MS14-064 Microsoft Windows OLE Package Manager Code Execution (metasploit)
- Microsoft Windows - OLE Remote Code Execution 'Sandworm' (MS14-060) (exploitdb)
- Microsoft Office 2007/2010 - OLE Arbitrary Command Execution (exploitdb)
- MS14-064 Microsoft Windows OLE Package Manager Code Execution Through Python (metasploit)

## Other vulnerabilities in Microsoft Windows 7

- [CVE-2015-1635](https://insights.sbomify.com/CVE-2015-1635/): Microsoft HTTP.sys Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-2360](https://insights.sbomify.com/CVE-2015-2360/): Microsoft Win32k Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6324](https://insights.sbomify.com/CVE-2014-6324/): Microsoft Kerberos Key Distribution Center (KDC) Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6332](https://insights.sbomify.com/CVE-2014-6332/): Microsoft Windows Object Linking & Embedding (OLE) Automation Array Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2014-4148](https://insights.sbomify.com/CVE-2014-4148/): Microsoft Windows Remote Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-6352 and fix it if it is affected.

What it is: CVE-2014-6352 is a high-severity code injection vulnerability in Microsoft Windows 7, published on 22 Oct 2014. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2014-6352 in the wild since at least 25 Feb 2022.

Affected product: Microsoft Windows 7. 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-2014-6352/ (Markdown: https://insights.sbomify.com/CVE-2014-6352/index.md)
```

## Sources

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

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