SecTor 2025 | Signature of Destruction: Outlook RCE Strikes Again
Why It Matters
Because the exploit works with stolen credentials and no user interaction, it gives attackers persistent, cross‑device control of corporate Outlook environments, forcing urgent remediation and tighter post‑auth defenses.
Key Takeaways
- •Remote code execution can be achieved via Outlook roaming signatures.
- •Microsoft Exchange synchronizes malicious custom forms without user interaction.
- •Recent patches only partially mitigate form injection and COM hijack flaws.
- •Roaming settings store JSON signatures that can embed executable payloads.
- •Credential theft enables zero‑click attacks across all synced Outlook devices.
Summary
The SecTor 2025 talk by Michael Berik of Morphoscans focused on a new attack chain that leverages Outlook’s roaming signature feature to achieve remote code execution (RCE) without any user clicks.
Berik recapped earlier Exchange‑based form‑injection bugs, COM‑object hijacking, and a calculator pop‑up exploit demonstrated at BlueHat. He then explained how Microsoft’s roaming settings store signatures as JSON blobs in Azure storage, which are automatically synced to every Outlook client. By injecting malicious HTML or RTF payloads into these blobs, an attacker who has stolen mailbox credentials can force the client to execute arbitrary code.
The presenter highlighted that the technique builds on previously patched vulnerabilities—Microsoft added prefix validation for form paths and suffix checks for COM methods, yet still allowed crafted strings to bypass controls. A “recall” form with a modified class ID caused a crash, illustrating the ease of weaponizing built‑in features. He also noted his recognition as Microsoft’s 2025 Most Valuable Researcher for uncovering such flaws.
The discovery widens the post‑authentication attack surface: any organization that enables roaming signatures now faces a zero‑click RCE risk. Enterprises must audit roaming settings, enforce strict signature sanitization, and consider disabling automatic sync until Microsoft hardens the underlying APIs.
Comments
Want to join the conversation?
Loading comments...