PHAR Deserialization in dompdf/dompdf
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| dompdf | dompdf/dompdf | affected |
|
No data.
No data available yet.
| Source | ID | Title |
|---|---|---|
Debian DLA |
DLA-3495-1 | php-dompdf security update |
Debian DLA |
DLA-3495-2 | php-dompdf regression update |
Debian DLA |
DLA-4427-1 | php-dompdf security update |
EUVD |
EUVD-2024-3197 | DomPDF before version 2.0.0 is vulnerable to PHAR deserialization due to a lack of checking on the protocol before passing it into the file_get_contents() function. An attacker who can upload files of any type to the server can pass in the phar:// protocol to unserialize the uploaded file and instantiate arbitrary PHP objects. This can lead to remote code execution, especially when DOMPdf is used with frameworks with documented POP chains like Laravel or vulnerable developer code. |
Github GHSA |
GHSA-577p-7j7h-2jgf | Deserialization of Untrusted Data in dompdf/dompdf |
Ubuntu USN |
USN-6277-1 | Dompdf vulnerabilities |
Ubuntu USN |
USN-6277-2 | Dompdf vulnerabilities |
No CVSS v4.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.4% (1.432% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dompdf Project
Dompdf Project dompdf |
|
| CPEs | cpe:2.3:a:dompdf_project:dompdf:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Dompdf Project
Dompdf Project dompdf |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dompdf
Dompdf dompdf |
|
| CPEs | cpe:2.3:a:dompdf:dompdf:*:beta3:*:*:*:*:*:* | |
| Vendors & Products |
Dompdf
Dompdf dompdf |
|
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | DomPDF before version 2.0.0 is vulnerable to PHAR deserialization due to a lack of checking on the protocol before passing it into the file_get_contents() function. An attacker who can upload files of any type to the server can pass in the phar:// protocol to unserialize the uploaded file and instantiate arbitrary PHP objects. This can lead to remote code execution, especially when DOMPdf is used with frameworks with documented POP chains like Laravel or vulnerable developer code. | |
| Title | PHAR Deserialization in dompdf/dompdf | |
| Weaknesses | CWE-502 | |
| References |
| |
| Metrics |
cvssV3_0
|