Microsoft Outlook Custom Forms Remote Code Execution
CVE-2024-21378 is an authenticated remote code execution vulnerability in Microsoft Outlook involving unsafe handling of synced custom form objects. According to the provided content, Outlook installs forms synchronized through MAPI using IPM.Microsoft.FolderDesign.FormsDescription objects and uses form properties such as PidTagOfflineAddressBookName and PidTagOfflineAddressBookDistinguishedName during installation. NetSPI found that a malicious form could abuse attachment handling, including path traversal via the PidTagAttachFilename property, to write arbitrary files under the local Outlook FORMS directory, and could also create arbitrary registry keys with default values under HKEY_CLASSES_ROOT during form installation. The content further states that Outlook contained a denylist in OLMAPI32.DLL intended to block dangerous COM registration paths, but this could be bypassed by supplying a leading backslash-style full subkey path such as CLSID{GUID}\InprocServer32. By combining arbitrary file write and arbitrary HKCR registry key creation, an attacker could register a COM object backed by an attacker-controlled DLL and cause Outlook to load it when the malicious form was triggered in the Windows thick client.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository provides a proof-of-concept exploit for CVE-2024-21378, a vulnerability in Microsoft Outlook (Exchange Online) that allows arbitrary code execution via malicious COM DLLs. The exploit consists of a single Python script (CVE-2024-21378.py) and a README with detailed instructions. The script sends a crafted HTTP POST request to the /ruler endpoint of a target Outlook/Exchange Online instance, delivering a malicious COM DLL as a form attachment. The attack requires a valid access token (typically obtained via phishing/vishing), the target's email address, and a compiled malicious DLL. User interaction in the Outlook thick client is required to trigger the payload, which results in the DLL being loaded and executed in the Outlook process. The repository is structured simply, with the Python script as the main entry point and the README providing context, usage instructions, and a disclaimer.
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.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Microsoft Outlook remote code execution vulnerability involving custom MAPI forms loading a malicious DLL from the FORMS directory.
A Microsoft Outlook remote code execution vulnerability referenced in connection with this detection content.
An authenticated remote code execution vulnerability in Microsoft Outlook involving malicious form objects and registry changes tied to InProcServer32 Outlook form installations.
A remote code execution vulnerability in Microsoft Outlook confirmed by Black Basta to be effective in production environments.
The version that knows your environment.
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.