Code execution via unterminated type-name buffer
Published Mar 2, 2020 · Updated Aug 4, 2024
Out-of-bounds write in PDFResurrect 0.12 through 0.19 allows local users to crash the process or execute code via a crafted PDF. In get_type in pdf.c, memcpy can fill the 32-byte static type-name buffer without a terminator, and the following delimiter scan writes a null byte beyond it. PDFResurrect must generate a summary of the crafted document; successful code runs with the invoking user's privileges.
Summary
What happened
Out-of-bounds write in PDFResurrect 0.12 through 0.19 allows local users to crash the process or execute code via a crafted PDF. In get_type in pdf.c, memcpy can fill the 32-byte static type-name buffer without a terminator, and the following delimiter scan writes a null byte beyond it. PDFResurrect must generate a summary of the crafted document; successful code runs with the invoking user's privileges.
The record
- CVE
- CVE-2020-9549
- Published
- Mar 2, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 2, 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
- PDFResurrect issue 8 trigger documentproof 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