Code execution via heap-based buffer overflow
Published Aug 13, 2024 · Updated Jul 10, 2025
Heap-based buffer overflow in Microsoft Office Visio allows local attackers to execute code after a user opens a crafted file. Microsoft identifies the weakness as CWE-122 but has not published the vulnerable parser, file structure, or overwrite operation that triggers the overflow. Exploitation requires user interaction and yields code execution in the context of the affected Office process; no network-listening service is implicated.
Summary
What happened
Heap-based buffer overflow in Microsoft Office Visio allows local attackers to execute code after a user opens a crafted file. Microsoft identifies the weakness as CWE-122 but has not published the vulnerable parser, file structure, or overwrite operation that triggers the overflow. Exploitation requires user interaction and yields code execution in the context of the affected Office process; no network-listening service is implicated.
The record
- CVE
- CVE-2024-38169
- Published
- Aug 13, 2024
- Updated
- Jul 10, 2025
- Vendor
- Microsoft
- Product
- Microsoft Office 2019
- Classifications
- CWE-122, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 13, 2024CVE publishedPublication date reported by the CVE source.
- Jul 10, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=19.0.0 <https://aka.ms/OfficeSecurityReleases
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo