Skip to main content
Mallory
HighExploited in the wildCISA KEVVulnerability

CVE-2015-1642: CTaskSymbol Use-After-Free in Microsoft Office OLE

Published Aug 15, 2015 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS53.1%99th percentile
CISA KEVYesAdded Mar 3, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2015-1642CWE-416

CVE-2015-1642 is a use-after-free vulnerability in the CTaskSymbol object within Microsoft Office's OLE (Object Linking and Embedding) implementation. The flaw exists in Office 2007 SP3, 2010 SP2, and 2013 SP1, and can be triggered by a specially crafted document. Exploitation allows remote attackers to execute arbitrary code in the context of the user opening the malicious document. The vulnerability was discovered by Yong Chuan, Koh of MWR Labs and detailed exploitation tactics were presented by Dominic Wang at ToorCon San Diego 2015.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation of this vulnerability allows remote code execution with the privileges of the user who opens the malicious document. This has been leveraged in targeted malware campaigns against high-profile organizations, enabling attackers to gain initial access, execute further payloads, or establish persistence within a target environment.

Mitigation

If you can’t patch tonight, do this now.

In addition to patching, organizations should implement standard mitigations such as disabling OLE object activation in Office documents from untrusted sources, using Protected View, and employing endpoint security solutions capable of detecting and blocking malicious documents. User awareness training to avoid opening suspicious attachments is also recommended.

Remediation

Patch, then assume compromise.

Apply the security updates provided by Microsoft for Office 2007 SP3, 2010 SP2, and 2013 SP1 that address CVE-2015-1642. Ensure all Office installations are fully patched and up to date. Microsoft regularly releases security bulletins and patches for such vulnerabilities.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationMicrosoft Officeapplication
FAQ

Frequently asked questions

Is CVE-2015-1642 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 3, 2022.
Is there a public exploit for CVE-2015-1642?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2015-1642.
Is there a patch for CVE-2015-1642?
Apply the security updates provided by Microsoft for Office 2007 SP3, 2010 SP2, and 2013 SP1 that address CVE-2015-1642. Ensure all Office installations are fully patched and up to date.
What products are affected by CVE-2015-1642?
Microsoft Corporation Microsoft Office.
How severe is CVE-2015-1642?
CVE-2015-1642 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 53.1% (99th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.