Code execution via stale cached descriptor pointer
Published Aug 19, 2021 · Updated Aug 4, 2024
Use-after-free in libpff_item_tree_create_node in libpff before 20180623 allows local users to execute code via a crafted PFF file. Recursive descriptor-tree processing can evict a cached descriptor value, but the function later reads identifier fields from the stale pointer instead of preserving them before cache-changing calls. Processing attacker-supplied PST, OST, or PAB content is required; crash inputs demonstrate a parser crash, while the CVE record also reports arbitrary code execution.
Summary
What happened
Use-after-free in libpff_item_tree_create_node in libpff before 20180623 allows local users to execute code via a crafted PFF file. Recursive descriptor-tree processing can evict a cached descriptor value, but the function later reads identifier fields from the stale pointer instead of preserving them before cache-changing calls. Processing attacker-supplied PST, OST, or PAB content is required; crash inputs demonstrate a parser crash, while the CVE record also reports arbitrary code execution.
The record
- CVE
- CVE-2020-18897
- Published
- Aug 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-416, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 19, 2021CVE 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.
Weakness, pattern, technique
Public exploit references
- huaf_libpff_item_tree.c:828_1.input.txtproof of concept · demonstrated
- huaf_libpff_item_tree.c:828_2.input.txtproof of concept · demonstrated
- huaf_libpff_item_tree.c:816_2.input.txtproof of concept · demonstrated
- huaf_libpff_item_tree.c:816_1.input.txtproof of concept · demonstrated
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