Command execution via unsanitized terminal escape sequences
Published Jan 9, 2020 · Updated Aug 6, 2024
Terminal escape injection in Error.cc in Poppler before 0.21.4 allows remote attackers to execute commands through a crafted PDF. The error function writes PDF-derived error text to callbacks or standard error without replacing control and non-ASCII bytes, allowing terminal escape sequences to reach a terminal emulator. Exploitation requires a local user to open the document in a Poppler-linked application, after which the terminal can change a window title, execute commands, or overwrite files with that user's privileges.
Summary
What happened
Terminal escape injection in Error.cc in Poppler before 0.21.4 allows remote attackers to execute commands through a crafted PDF. The error function writes PDF-derived error text to callbacks or standard error without replacing control and non-ASCII bytes, allowing terminal escape sequences to reach a terminal emulator. Exploitation requires a local user to open the document in a Poppler-linked application, after which the terminal can change a window title, execute commands, or overwrite files with that user's privileges.
The record
- CVE
- CVE-2012-2142
- Published
- Jan 9, 2020
- Updated
- Aug 6, 2024
- Vendor
- Libslirp Project
- Product
- Poppler
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 9, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=before 0.21.4
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