Code execution via stale pointer after reallocation
Published Mar 19, 2020 · Updated Aug 5, 2024
Use-after-free in HncBD90 in Hancom Office NEO 9.6.1.9403 allows context-dependent attackers to execute code via a crafted .xlsx file. HncBD90 reallocates a workbook-driven buffer but leaves an interior pointer unchanged, then dereferences that pointer after the old allocation has been freed. Exploitation requires a user to open the malicious workbook, and successful memory corruption runs code in the application context.
Summary
What happened
Use-after-free in HncBD90 in Hancom Office NEO 9.6.1.9403 allows context-dependent attackers to execute code via a crafted .xlsx file. HncBD90 reallocates a workbook-driven buffer but leaves an interior pointer unchanged, then dereferences that pointer after the old allocation has been freed. Exploitation requires a user to open the malicious workbook, and successful memory corruption runs code in the application context.
The record
- CVE
- CVE-2019-16337
- Published
- Mar 19, 2020
- Updated
- Aug 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 19, 2020CVE publishedPublication date reported by the CVE source.
- Aug 5, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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.
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