CVE-2024-25117: php-svg-lib lacks path validation on font through SVG inline styles

Published Feb 21, 2024
·
Updated

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

3 affected componentsFixes available
composer/phenx/php-svg-lib<0.5.2
0.5.2
All of the following
dompdf php-svg-lib<0.5.2
PHP PHP<8.0.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/phenx/php-svg-lib to a version that resolves this vulnerability.

    Fixed in 0.5.2
  2. Upgrade

    Upgrade php-svg-lib to a version that resolves this vulnerability.

    Fixed in 0.5.2
  3. 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
  4. 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

Feb 21, 2024
CVE Published
via MITRE·04:25 PM
Data Sourced
via MITRE·04:25 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:15 PM
RemedyDescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·06:04 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

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.

2

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.

3

Which versions of PHP are affected by CVE-2024-25117?

CVE-2024-25117 affects PHP versions prior to 8.0.

4

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.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203