Loading vulnerability…
CVE-2015-1770 is a remote code execution vulnerability in Microsoft Office 2013 SP1 and Office 2013 RT SP1 caused by the use of uninitialized memory when processing a crafted Office document, including weaponized RTF content. Successful exploitation can allow an attacker to execute arbitrary code in the context of the user who opens the malicious document. The vulnerability was addressed by Microsoft in June 2015 as part of MS15-059 and has been observed in targeted spearphishing operations delivering malicious Office 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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A patched RTF-related Microsoft Office vulnerability referenced as part of a set of older exploits used to weaponize RTF documents in espionage campaigns; the report does not provide technical details beyond inclusion in the exploit set.
A Microsoft Office remote code execution vulnerability delivered via malicious RTF documents and used in Carbanak spearphishing attacks.
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.