CVE-2024-20677 json
Microsoft Office Remote Code Execution Vulnerability
published 2024-01-09 2 y ago modified 2026-06-17 4 mo ago also EUVD-2024-18392
- cvss
- 7.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 3.3%
- EPSS 3.3% chance of exploitation in 30 days, percentile 88%
- public exploits
- 0
- none known
Summary
A security vulnerability exists in FBX that could lead to remote code execution. To mitigate this vulnerability, the ability to insert FBX files has been disabled in Word, Excel, PowerPoint and Outlook for Windows and Mac. Versions of Office that had this feature enabled will no longer have access to it. This includes Office 2019, Office 2021, Office LTSC for Mac 2021, and Microsoft 365. As of February 13, 2024, the ability to insert FBX files has also been disabled in 3D Viewer. 3D models in Office documents that were previously inserted from a FBX file will continue to work as expected unless the Link to File option was chosen at insert time. This change is effective as of the January 9, 2024 security update.
Patch / fix
- Microsoft 3D Viewer 7.2401.29012.0
- Microsoft Microsoft Office LTSC for Mac 2021 16.81.24011420
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
3.26% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| CNA | 3.1 | 7.8 | CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected products
- Microsoft 3D Viewer
- Microsoft Microsoft Office 2019
- Microsoft Microsoft 365 Apps for Enterprise
- Microsoft Microsoft Office LTSC for Mac 2021
- Microsoft Microsoft Office LTSC 2021
Classification
- Weakness
-
- CWE-122 Heap-based Buffer Overflow
References
-
msrc.microsoft.com
/update-guide/vulnerability/CVE-2024-20677
vendor-advisory, patch
Sources
- CVE List CVE-2024-20677
- NVD CVE-2024-20677
Fencer Vulns 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.