Remote code execution via unchecked PHAR resource protocol
Published Nov 15, 2024 · Updated Nov 18, 2024
PHAR deserialization in dompdf before 2.0.0 allows remote attackers to execute code through an attacker-controlled resource URI. Resource-loading paths pass an insufficiently validated phar:// URI to file_get_contents(), causing PHP to deserialize an uploaded archive and instantiate arbitrary objects. Exploitation requires PHP before 8.0.0, control of rendered HTML, arbitrary file upload, and a usable PHP object-injection chain in the host application.
Summary
What happened
PHAR deserialization in dompdf before 2.0.0 allows remote attackers to execute code through an attacker-controlled resource URI. Resource-loading paths pass an insufficiently validated phar:// URI to file_get_contents(), causing PHP to deserialize an uploaded archive and instantiate arbitrary objects. Exploitation requires PHP before 8.0.0, control of rendered HTML, arbitrary file upload, and a usable PHP object-injection chain in the host application.
The record
- CVE
- CVE-2021-3838
- Published
- Nov 15, 2024
- Updated
- Nov 18, 2024
- Vendor
- dompdf
- Product
- dompdf
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 15, 2024CVE publishedPublication date reported by the CVE source.
- Nov 18, 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=0 <2.0.0
- Affected versionversion=unspecified <2.0.0
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
- Huntr PHAR deserialization proof of conceptproof 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