Vigilbase CVEConnect your agent

Microsoft SharePoint Server Remote Code Execution Vulnerability

Not in CISA KEVCVE-2024-38024CWE-502

Not confirmed exploited. 2 of 8 rule sources name it; Cloudflare blocks by default.

Edge rules
2/8
Our test
No exploit yet
CVSS
7.2
EPSS
45.2% Top 1%
Posts, 14d
02026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts2026-11-03: 0 posts
Published
2024-07-09

Microsoft SharePoint Server Remote Code Execution Vulnerability

Ask Vigil

AI · answers from this page
Ask about CVE-2024-38024: who's covered, what to patch first, how vendors compare. I cite sources and won't help with attacks.

Workers AI (Llama 3.3). Can be wrong: check the cited source.

Severity, decoded

CVSS 3.1
High · 7.2 / 10

Exploitable over the network, with high privileges and no user interaction, leading to full loss of confidentiality, integrity and availability.

Over the internetAdmin login neededNo user actionWorks reliablyFull compromise
How the score is built8 metrics
  • Attack vectorAn attacker can reach it over the internet; no access to your network needed.
    Network
  • Attack complexityNo special conditions are needed; the attack works reliably.
    Low
  • Privileges requiredThe attacker needs an administrator-level account.
    High
  • User interactionNo one has to click or open anything; the attack works on its own.
    None
  • ScopeThe damage stays within the vulnerable component.
    Unchanged
  • Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.
    High
  • Integrity impactAn attacker can change any data or files the affected component protects.
    High
  • Availability impactAn attacker can take the component down completely or keep it from serving anyone.
    High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Also in the vector: Exploit code maturity: Unproven · Remediation level: Official fix · Report confidence: Confirmed

CISA's assessmentSSVC, from the CVE record
ExploitationNone

CISA has seen no public exploit and no attacks.

AutomatableNo

At least one step needs hands-on work, which slows mass attacks.

Technical impactTotal

A successful attack gives full control over the affected software or all of its data.

Public exploits

None found
0 Metasploit0 Exploit-DB0 Scanner template0 GitHub PoCs

No exploit in Exploit-DB or Metasploit, and no scanner template. That lowers, but doesn't remove, the chance of mass exploitation.

Timeline

  1. 2024-07-09
    CVE published
    CVE List
  2. 2024-08-13
    F5 ships a rule
    Microsoft SharePoint bdcm Remote Code Execution (2)
  3. 2025-01-06
    Cloudflare ships a rule
    Microsoft SharePoint - Remote Code Execution - CVE:CVE-2024-38094, CVE:CVE-2024-38024, CVE:CVE-2024-38023

Social

2026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts2026-11-03: 0 posts

No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.

Vendor statements

Quoted
CloudflareWAF Managed Rules1 quoteBlocks by default

First rule 2025-01-06, 181 days after the CVE was published.

2025-01-06New rule…dfe93d7bDefault: BlockSource
Microsoft SharePoint - Remote Code Execution - CVE:CVE-2024-38094, CVE:CVE-2024-38024, CVE:CVE-2024-38023. Previous action: Log. New action: Block. New Detection
AWSAWS WAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.

Microsoft AzureFront Door and Application Gateway WAF (DRS)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. The rule tables name CVEs but carry no dates, so Azure is left out of every time-to-rule figure.

Google CloudCloud Armor preconfigured WAF rulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. Google names few CVEs: the release notes start in May 2024 and the rules reference lists CVEs without dates. Its cve-canary rules are opt-in.

FastlyNext-Gen WAF virtual patchesBefore feed history

The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.

F5Attack signatures (Distributed Cloud WAF)4 quotesRule published

First rule 2024-08-13, 35 days after the CVE was published.

2024-08-13New rule200104976Source
Added: signature 200104976 "Microsoft SharePoint bdcm Remote Code Execution (2)" (Server Side Code Injection, risk High), systems: Outlook Web Access, Microsoft Windows, IIS. References: CVE-2024-38094, CVE-2024-38024, CVE-2024-38023.
2024-08-13New rule200104977Source
Added: signature 200104977 "Microsoft SharePoint bdcm Remote Code Execution (1)" (Server Side Code Injection, risk High), systems: Outlook Web Access, Microsoft Windows, IIS. References: CVE-2024-38094, CVE-2024-38024, CVE-2024-38023.
2024-09-17Updated200104976Source
Updated: signature 200104976 "Microsoft SharePoint bdcm Remote Code Execution (2)" (Server Side Code Injection, risk High), systems: Outlook Web Access, Microsoft Windows, IIS. References: CVE-2024-38094, CVE-2024-38024, CVE-2024-38023.
2024-09-17Updated200104977Source
Updated: signature 200104977 "Microsoft SharePoint bdcm Remote Code Execution (1)" (Server Side Code Injection, risk High), systems: Outlook Web Access, Microsoft Windows, IIS. References: CVE-2024-38094, CVE-2024-38024, CVE-2024-38023.
AkamaiApp & API Protector (Adaptive Security Engine)No public source

This vendor publishes no machine-readable rule changelog we can check.

OWASP CRSCore Rule Set (open source, used inside many WAFs)No public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. CRS rarely names CVEs: it relies on generic detections. Our own lab measures what it actually blocks.