Memory disclosure via uninitialized out-of-bounds read
Published Jun 9, 2020 · Updated Aug 4, 2024
Out-of-bounds read in Microsoft Project allows context-dependent attackers to disclose process memory through a crafted Project file. While parsing the file, Project uses an uninitialized variable to read beyond an allocated memory boundary and exposes adjacent memory contents. Exploitation requires a user to open the malicious file; the reported consequence is memory disclosure, not data modification or service interruption.
Summary
What happened
Out-of-bounds read in Microsoft Project allows context-dependent attackers to disclose process memory through a crafted Project file. While parsing the file, Project uses an uninitialized variable to read beyond an allocated memory boundary and exposes adjacent memory contents. Exploitation requires a user to open the malicious file; the reported consequence is memory disclosure, not data modification or service interruption.
The record
- CVE
- CVE-2020-1322
- Published
- Jun 9, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Microsoft Office
- Classifications
- CWE-125, CWE-908, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=2019 for 32-bit editions
- Affected versionversion=2019 for 64-bit editions
What conditions does exploitation require?
What is affected?
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