Loading vulnerability…
CVE-2015-2545 is a memory-corruption vulnerability in Microsoft Office EPS image processing, specifically associated with EPS parsing in the EPSIMP32.FLT component. Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, and Office 2013 RT SP1 can be induced to execute attacker-controlled code when processing a specially crafted Encapsulated PostScript image embedded in an Office document, including MHTML/Web Archive-delivered documents.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
12 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A specific vulnerability exploited via a malicious MHTML document to deliver the TidePool malware used by APT15.
A remote code execution vulnerability in Microsoft Office triggered via a crafted EPS file.
A Microsoft Office-related vulnerability advertised as supported by the Microsoft Word Intruder exploit pack.
Arbitrary code execution via a specially crafted EPS image file; exploited by multiple APT groups despite being patched in 2015.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.