HighGHSA-634x-pc3q-cf4cCVE-2022-29221

PHP Code Injection by malicious block or filename in Smarty

Published 25 May 2022 · Updated 21 Feb 2024

Affected packages

Affected
<3.1.45
Fixed in
3.1.45
Update to the fixed version for your release line, for example:composer require smarty/smarty:^3.1.45
Affected
>=4.0.0 <4.1.1
Fixed in
4.1.1
Update to the fixed version for your release line, for example:composer require smarty/smarty:^4.1.1

Details

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:

Is GHSA-634x-pc3q-cf4c in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected smarty/smarty, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.