Skip to content

Twig may load a template outside a configured directory when using the filesystem loader

High severity GitHub Reviewed Published Sep 28, 2022 in twigphp/Twig • Updated Jan 27, 2023

Package

composer twig/twig (Composer)

Affected versions

>= 1.0.0, < 1.44.7
>= 2.0.0, < 2.15.3
>= 3.0.0, < 3.4.3

Patched versions

1.44.7
2.15.3
3.4.3

Description

Description

When using the filesystem loader to load templates for which the name is a user input, it is possible to use the source or include statement to read arbitrary files from outside the templates directory when using a namespace like @somewhere/../some.file (in such a case, validation is bypassed).

Resolution

We fixed validation for such template names.

Even if the 1.x branch is not maintained anymore, a new version has been released.

Credits

We would like to thank Dariusz Tytko for reporting the issue and Fabien Potencier for fixing the issue.

References

@fabpot fabpot published to twigphp/Twig Sep 28, 2022
Published by the National Vulnerability Database Sep 28, 2022
Published to the GitHub Advisory Database Sep 30, 2022
Reviewed Sep 30, 2022
Last updated Jan 27, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.329%
(72nd percentile)

Weaknesses

CVE ID

CVE-2022-39261

GHSA ID

GHSA-52m2-vc4m-jj33

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.