Skip to content
Fencer Intel
high 8.8

CVE-2024-38189 kev in the critical feed json

Microsoft Project Remote Code Execution Vulnerability

published 2y ago modified 4mo ago also EUVD-2024-37158

cvss
8.8
version 3.1, CNA
cisa kev
Exploited
added 2024-08-13
epss
8.2%
EPSS 8.2% chance of exploitation in 30 days, percentile 94%
public exploits
0
none known

Summary

Microsoft Project Remote Code Execution Vulnerability

Patch / fix

cisa required action Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

  • Microsoft Microsoft Project 2016 16.0.5461.1001

Is CVE-2024-38189 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. 0-day patched (Project Zero)
  2. Added to CISA KEV
  3. Published
  4. CISA SSVC: exploitation active
  5. CISA patch deadline

Known exploited

Added
2y ago
Patch by
2024-09-03 (2y ago)
Ransomware
Not known
Required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Vendor, product
Microsoft, Project
CISA name
Microsoft Project Remote Code Execution Vulnerability

Zero-day

Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.

Patched
2024-08-13
Details
project zero tracker

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
2y ago

Exploit prediction

8.19% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • Microsoft Microsoft Office 2019
  • Microsoft Microsoft 365 Apps for Enterprise
  • Microsoft Microsoft Project 2016
  • Microsoft Microsoft Office LTSC 2021

Classification

Weakness
  • CWE-20 Improper Input Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.