Local code execution via malformed metafile
Published May 11, 2020 · Updated Aug 4, 2024
Use-after-free in libEMF 1.0.11 and earlier allows local users to execute code by supplying a malformed EMF file. The upstream disclosure does not identify the affected parser function, freed object, or stale access within the EMF-processing path. A consuming application must parse the crafted file, so exploitation requires user interaction or an equivalent local file-processing path.
Summary
What happened
Use-after-free in libEMF 1.0.11 and earlier allows local users to execute code by supplying a malformed EMF file. The upstream disclosure does not identify the affected parser function, freed object, or stale access within the EMF-processing path. A consuming application must parse the crafted file, so exploitation requires user interaction or an equivalent local file-processing path.
The record
- CVE
- CVE-2020-11866
- Published
- May 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 11, 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?
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