CVE-2024-25117: php-svg-lib lacks path validation on font through SVG inline styles
Summary php-svg-lib fails to validate that font-family doesn't contain a PHAR url, which might leads to RCE on PHP < 8.0, and doesn't validate if external references are allowed. This might leads to bypass of restrictions or RCE on projects that are using it, if they do not strictly revalidate the fontName that is passed by php-svg-lib.
Details The Style::fromAttributes(), or the Style::parseCssStyle() should check the content of the font-family and prevents it to use a PHAR url, to avoid passing an invalid and dangerous fontName value to other libraries. The same check as done in the Style::fromStyleSheets might be reused :
if ( \arraykeyexists("font-family", $styles) && ( \strtolower(\substr($this->href, 0, 7)) === "phar://" || ($this->document->allowExternalReferences === false && \strtolower(\substr($this->href, 0, 5)) !== "data:") ) ) { unset($style["font-family"]); }
PoC
Parsing the following SVG :
<?xml version="1.0" encoding="UTF-8" standalone="no"?> <svg xmlns:svg="http://www.w3.org/2000/svg" xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="200" height="200"> <text x="20" y="35" style="color:red;font-family:phar:///path/to/whatever.phar/blaklis;">My</text> </svg>
will pass the phar:///path/to/whatever.phar/blaklis as $family in SurfaceCpdf::setFont, which is then passed to the canvas selectFont as a $fontName.
Impact Libraries using this library as a dependency might be vulnerable to some bypass of restrictions, or even RCE, if they do not double check the value of the fontName that is passed by php-svg-lib
Other sources
php-svg-lib is a scalable vector graphics (SVG) file parsing/rendering library. Prior to version 0.5.2, php-svg-lib fails to validate that font-family doesn't contain a PHAR url, which might leads to RCE on PHP < 8.0, and doesn't validate if external references are allowed. This might leads to bypass of restrictions or RCE on projects that are using it, if they do not strictly revalidate the fontName that is passed by php-svg-lib. The Style::fromAttributes(), or the Style::parseCssStyle() should check the content of the font-family and prevents it to use a PHAR url, to avoid passing an invalid and dangerous fontName value to other libraries. The same check as done in the Style::fromStyleSheets might be reused. Libraries using this library as a dependency might be vulnerable to some bypass of restrictions, or even remote code execution, if they do not double check the value of the fontName that is passed by php-svg-lib. Version 0.5.2 contains a fix for this issue.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
composer/phenx/php-svg-libto a version that resolves this vulnerability.Fixed in 0.5.2 - Upgrade
Upgrade
php-svg-libto a version that resolves this vulnerability.Fixed in 0.5.2 - Configuration
Ensure php-svg-lib is configured so that inline/external references are not allowed (i.e., allowExternalReferences === false). This aligns with the check that blocks references unless the reference is a data: URI.
php-svg-lib SVG parsing allowExternalReferences = false - Configuration
Apply/ensure the validation that prevents using a PHAR URL in font-family values during parsing: reject when font-family (or href used for font-family) begins with "phar://" (e.g., by checking lowercase substr(...) equals "phar://"), and unset/remove the font-family attribute when it is present.
php-svg-lib Style parsing (Style::fromAttributes / Style::parseCssStyle) font-family validation = block phar://
Event History
Frequently Asked Questions
What is the severity of CVE-2024-25117?
CVE-2024-25117 is considered a critical vulnerability due to its potential for remote code execution (RCE) on affected PHP versions.
How do I fix CVE-2024-25117?
To fix CVE-2024-25117, update the php-svg-lib package to version 0.5.3 or higher.
Which versions of PHP are affected by CVE-2024-25117?
CVE-2024-25117 affects PHP versions prior to 8.0.
What impact does CVE-2024-25117 have on software projects?
CVE-2024-25117 may allow attackers to bypass restrictions or execute arbitrary code, posing a serious threat to the security of affected projects.
Is there a known fix or workaround for CVE-2024-25117 besides updating?
There are no known workarounds that effectively mitigate CVE-2024-25117, so upgrading is the recommended course of action.