Microsoft SharePoint Remote Code Execution Vulnerability
Why It Matters
Analysis dossierWhy It Matters
Microsoft SharePoint Remote Code Execution Vulnerability
Immediate Attention
Yes
Unknown
Risk basis: CISA KEV exploitation signal; Microsoft or Microsoft-managed product relevance; HIGH severity; Known exploitation signal from CISA KEV or ransomware metadata
Affected Products & Remediation
1 source-backed product- microsoft sharepoint server · 2016; 2019 · NVD CPE · Source
Vendor or catalog guidance (source)
- CISA KEV: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Known exploitation (source facts)
Only what a source states. Unknown means no source has said either way; it is not "not exploited".
- CISA KEV
- Listed
- Exploited (source statement)
- Yes
- Publicly disclosed (source)
- Unknown
CISA required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Suggested hunting (rule-based inference)
SecOps Signal recommendation (rule-based inference). These steps are hunting hypotheses from the vulnerability class; they do not state or imply that exploitation occurred here or anywhere.
Matched kev-network-exposure (CVSS AV:N, CISA KEV Listed); microsoft-enterprise (Affected product: microsoft sharepoint server, Vendor: microsoft)
Exposure
- Identify assets with the exact CVE and confirm the affected product/version against the advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · KEV listing raises urgency, but inventory is needed to establish local exposure. · Rule kev-network-exposure
- Identify affected Microsoft products and compare local builds with the MSRC advisory.Telemetry: DeviceTvmSoftwareVulnerabilities · The MSRC product/build mapping establishes applicability. · Rule microsoft-enterprise
Exploitation evidence
- Review relevant edge or application access logs for unusual requests around the advisory window.Telemetry: CommonSecurityLog · Log review is a hunting hypothesis; KEV listing alone does not show local exploitation. · Rule kev-network-exposure
Show more (2)
Exploitation evidence
- Review the advisory's documented behavior on matching hosts before selecting a hunt.Telemetry: DeviceProcessEvents · Product family alone does not justify a CVE-specific detection. · Rule microsoft-enterprise
Response
- Recheck the affected assets after the source-stated mitigation or update is applied.Telemetry: DeviceTvmSoftwareVulnerabilities · A follow-up inventory check verifies local remediation. · Rule kev-network-exposure
CISA KEV Record
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Change History & Source Data
— No recorded material change
- CNA / source
- secure@microsoft.com
- Record status · verification
- UPDATED · Microsoft primary source linked; CISA KEV confirmed
- CPE
- cpe:2.3:a:microsoft:sharepoint_server:-:*:*:*:subscription:*:*:*, cpe:2.3:a:microsoft:sharepoint_server:2016:*:*:*:enterprise:*:*:*, cpe:2.3:a:microsoft:sharepoint_server:2019:*:*:*:*:*:*:*
Evidence & Provenance
Linked by the query's stored exact CVE association. Review required tables and validation status before use.
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2024-38094"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc