CVE-2023-24813: URI validation failure on SVG parsing. Bypass of CVE-2023-23924
Summary Due to the difference in the attribute parser of Dompdf and php-svg-lib, an attacker can still call arbitrary URLs with arbitrary protocols.
Details Dompdf parses the href attribute of image tags with the following code:
src/Image/Cache.php line 135-150 php function ($parser, $name, $attributes) use ($options, $parsedurl, $fullurl) { if (strtolower($name) === "image") { $attributes = arraychangekeycase($attributes, CASELOWER); $url = $attributes["xlink:href"] ?? $attributes["href"]; if (!empty($url)) { $innerfullurl = Helpers::buildurl($parsedurl["protocol"], $parsedurl["host"], $parsedurl["path"], $url); if ($innerfullurl === $fullurl) { throw new ImageException("SVG self-reference is not allowed", EWARNING); } [$resolvedurl, $type, $message] = self::resolveurl($url, $parsedurl["protocol"], $parsedurl["host"], $parsedurl["path"], $options); if (!empty($message)) { throw new ImageException("This SVG document references a restricted resource. $message", EWARNING); } } } },
As you can see from the code snippet above, it respects xlink:href even if href is specified. php $url = $attributes["xlink:href"] ?? $attributes["href"];
However, php-svg-lib, which is later used to parse the svg file, parses the href attribute with the following code:
src/Svg/Tag/Image.php line 51-57 php if (isset($attributes['xlink:href'])) { $this->href = $attributes['xlink:href']; }
if (isset($attributes['href'])) { $this->href = $attributes['href']; }
Since href is respected if both xlink:href and href is specified, it's possible to bypass the protection on the Dompdf side by providing an empty xlink:href attribute.
Impact An attacker can exploit the vulnerability to call arbitrary URLs with arbitrary protocols if they provide an SVG file to the Dompdf. In PHP versions before 8.0.0, it leads to arbitrary unserialize, which will lead, at the very least, to arbitrary file deletion and might lead to remote code execution, depending on available classes.
Other sources
Dompdf is an HTML to PDF converter written in php. Due to the difference in the attribute parser of Dompdf and php-svg-lib, an attacker can still call arbitrary URLs with arbitrary protocols. Dompdf parses the href attribute of image tags and respects xlink:href even if href is specified. However, php-svg-lib, which is later used to parse the svg file, parses the href attribute. Since href is respected if both xlink:href and href is specified, it's possible to bypass the protection on the Dompdf side by providing an empty xlink:href attribute. An attacker can exploit the vulnerability to call arbitrary URLs with arbitrary protocols if they provide an SVG file to the Dompdf. In PHP versions before 8.0.0, it leads to arbitrary unserialize, which will lead, at the very least, to arbitrary file deletion and might lead to remote code execution, depending on available classes. This vulnerability has been addressed in commit 95009ea98 which has been included in release version 2.0.3. Users are advised to upgrade. There are no known workarounds for this vulnerability.
URI validation failure on SVG parsing. Bypass of CVE-2023-23924
— Packagist
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/dompdf/dompdfto a version that resolves this vulnerability.Fixed in 2.0.3 - Upgrade
Upgrade
dompdf/dompdfto a version that resolves this vulnerability.Fixed in 2.0.3Patch 95009ea98
Event History
Frequently Asked Questions
What is CVE-2023-24813?
CVE-2023-24813 is a critical vulnerability in Dompdf, an HTML to PDF converter written in PHP, that allows an attacker to call arbitrary URLs with arbitrary protocols.
How severe is CVE-2023-24813?
CVE-2023-24813 has a severity score of 9.8 (critical).
Which version of Dompdf is affected by CVE-2023-24813?
Dompdf version 2.0.2 is affected by CVE-2023-24813.
How can an attacker exploit CVE-2023-24813?
An attacker can exploit CVE-2023-24813 by manipulating the href attribute of image tags to call arbitrary URLs with arbitrary protocols.
Are there any references related to CVE-2023-24813?
Yes, you can find more information about CVE-2023-24813 in the following references: - [GitHub Commit](https://github.com/dompdf/dompdf/commit/95009ea98230f9b084b040c34e3869ef3dccc9aa) - [GitHub Security Advisory](https://github.com/dompdf/dompdf/security/advisories/GHSA-56gj-mvh6-rp75)