CVE-2024-38023 is a remote code execution vulnerability in Microsoft SharePoint Server. A remote authenticated attacker with SharePoint permissions at the Site Owner level or higher can exploit the flaw by uploading a specially crafted file and then issuing a specially crafted API request that causes deserialization of parameters from that file. Successful exploitation results in execution of attacker-controlled code in the context of the SharePoint server. The available information indicates the vulnerable condition is tied to unsafe deserialization during SharePoint server-side processing of attacker-supplied file parameters.
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.
Remote code execution vulnerability in Microsoft SharePoint Server that allows an authenticated attacker with Site Owner or higher privileges to execute code via a crafted file upload and malicious API request leading to deserialization.
Remote code execution vulnerability in Microsoft SharePoint Server requiring authenticated Site Owner permissions.
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.