Microsoft Project Remote Code Execution Vulnerability
Why It Matters
Analysis dossierWhy It Matters
Microsoft Project 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; Source-confirmed exploitation or CISA KEV/ransomware metadata
Affected Products & Remediation
4 source-backed productsVendor 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); user-interaction-client (CVSS AV:N, CVSS UI:R)
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 endpoints reporting this CVE, especially those used for email and web browsing.Telemetry: DeviceTvmSoftwareVulnerabilities · A network vector that needs user interaction points at user-facing client software. · Rule user-interaction-client
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 unusual child processes started by the affected client application on affected endpoints.Telemetry: DeviceProcessEvents · Hunting hypothesis from the CVSS vector; it does not show that exploitation occurred. · Rule user-interaction-client
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:365_apps:-:*:*:*:enterprise:*:*:*, cpe:2.3:a:microsoft:office_2019:-:*:*:*:*:*:x64:*, cpe:2.3:a:microsoft:office_2019:-:*:*:*:*:*:x86:*, cpe:2.3:a:microsoft:office_long_term_servicing_channel:2021:*:*:*:*:*:x64:*, cpe:2.3:a:microsoft:office_long_term_servicing_channel:2021:*:*:*:*:*:x86:*, cpe:2.3:a:microsoft:project_2016:*:*:*:*:*:*:*:*
Evidence & Provenance
Linked by the query's stored exact CVE association. Review required tables and validation status before use.
DeviceTvmSoftwareVulnerabilities| where CveId == "CVE-2024-38189"| project DeviceId, DeviceName, OSPlatform, OSVersion, SoftwareVendor, SoftwareName, SoftwareVersion, CveId, VulnerabilitySeverityLevel, RecommendedSecurityUpdate, RecommendedSecurityUpdateId| sort by VulnerabilitySeverityLevel desc