Cyber Resilience

CVE-2024-25117

Deserialization in Dompdf Php-Svg-Lib ≤ 0.5.2

DeserializationPath Traversal
Published
21 February 2024
Modified
17 June 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L
EPSS Score 0.0093 57th percentile
Risk Priority 52 floored blend · peak EPSS

Summary

CVE-2024-25117 is a medium-severity External Control of File Name or Path (CWE-73) vulnerability in Dompdf Php-Svg-Lib. Its CVSS base score is 6.8 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Local System (T1005); ranked in the top 43% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A05:2025 InjectionA06:2025 Insecure DesignA08:2025 Software or Data Integrity Failures

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-73CWE-502CWE-610

Related Threats

MITRE ATT&CK Enterprise Techniques

T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1552 Unsecured Credentials Credential Access
Adversaries may search compromised systems to find and obtain insecurely stored credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-50252Same product: Dompdf Php-Svg-Lib
CVE-2016-3078Same product: Php Php
CVE-2026-6722Same product: Php Php
CVE-2026-7261Same product: Php Php
CVE-2024-11235Same product: Php Php
CVE-2025-1217Same product: Php Php
CVE-2026-7568Same product: Php Php
CVE-2026-7258Same product: Php Php
CVE-2026-6104Same product: Php Php
CVE-2025-14177Same product: Php Php

Affected Assets

dompdf
php-svg-lib
≤ 0.5.2

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 2 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

Enforces access authorizations so externally supplied references cannot reach resources outside the intended sphere.

AC-4 Information Flow Enforcement good match

Controls information flow between security domains, blocking resolution of external references to unintended spheres.

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can uncover deserialization flaws before deployment.

SI-10 Information Input Validation good match

Input validation directly rejects or sanitizes untrusted path strings before they reach filesystem operations.

AC-6 Least Privilege partial match

Least-privilege limits the set of files or directories any subject can affect, shrinking the blast radius of a path-control flaw.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles such as safe deserialization and input sanitization structurally prevent the weakness from being introduced.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure SDLC practices include input validation and path sanitization that eliminate this weakness.

PR.AA-05 mostly match
prevents

Least-privilege file authorization directly limits damage from externally controlled paths.

DE.CM-09 partial match
prevents

Runtime monitoring of software and data flows can detect anomalous external resource accesses that result from this weakness.

PR.IR-01 partial match
prevents

Network segmentation and access controls limit the blast radius when an external reference escapes its intended sphere.

PR.PS-02 none match
prevents

PR.PS-02 addresses only post-deployment updates/patching and cannot prevent introduction of unsafe deserialization code, yet it can remediate some instances when the flaw exists in outdated libraries or components.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect path-traversal issues but does not itself implement preventive controls.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and path-handling controls that directly prevent external file/path manipulation.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against untrusted input influencing file operations.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles discourage unsafe path construction but do not prescribe concrete file-name controls.

A.8.28 Secure coding partial match
prevents

Secure coding standards require canonicalization, allow-listing, and bounds checks on file paths, directly eliminating CWE-73.

A.8.3 Information access restriction partial match
mitigates

Information access restriction limits which files can be reached, indirectly reducing impact of path manipulation.

Hardening callouts derived

Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).

Oracle Linux 8 (1 rule)
  • V-248577 OL 8 must enable kernel parameters to enforce Discretionary Access Control (DAC) on symlinks. prevents CWE-610

References