Skip to content

PHP Code Injection by malicious block or filename in Smarty

High severity GitHub Reviewed Published May 17, 2022 in smarty-php/smarty • Updated Jan 27, 2023

Package

composer smarty/smarty (Composer)

Affected versions

< 3.1.45
>= 4.0.0, < 4.1.1

Patched versions

3.1.45
4.1.1

Description

Impact

Template authors could inject php code by choosing a malicous {block} name or {include} file name. Sites that cannot fully trust template authors should update asap.

Patches

Please upgrade to the most recent version of Smarty v3 or v4.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

References

Are there any links users can visit to find out more?

For more information

If you have any questions or comments about this advisory:

References

@wisskid wisskid published to smarty-php/smarty May 17, 2022
Published by the National Vulnerability Database May 24, 2022
Published to the GitHub Advisory Database May 25, 2022
Reviewed May 25, 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.299%
(70th percentile)

Weaknesses

CVE ID

CVE-2022-29221

GHSA ID

GHSA-634x-pc3q-cf4c

Source code

Credits

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