HighGHSA-w5hr-jm4j-9jvqCVE-2021-26119
Sandbox escape through template_object in smarty
Published 2 Mar 2021 · Updated 3 Dec 2024
Affected package
smarty/smartyComposer
- Affected
- <3.1.39
- Fixed in
- 3.1.39
Update to the fixed version for your release line, for example:
composer require smarty/smarty:^3.1.39Details
Sandbox protection could be bypassed through access to an internal Smarty object that should have been blocked. Sites that rely on Smarty Security features should upgrade as soon as possible. Please upgrade to 3.1.39 or higher.
Is GHSA-w5hr-jm4j-9jvq 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
- Linkgithub.com/smarty-php/smarty/security/advisories/GHSA-w5hr-jm4j-9jvq
- Advisorynvd.nist.gov/vuln/detail/CVE-2021-26119
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/smarty/smarty/CVE-2021-26119.yaml
- Linkgithub.com/smarty-php/smarty
- Linkgithub.com/smarty-php/smarty/blob/master/CHANGELOG.md
- Linklists.debian.org/debian-lts-announce/2021/04/msg00004.html
- Linklists.debian.org/debian-lts-announce/2021/04/msg00014.html
- Linksecurity.gentoo.org/glsa/202105-06
- Linksrcincite.io/blog/2021/02/18/smarty-template-engine-multiple-sandbox-escape-vulnerabilities.html
- Linkwww.debian.org/security/2022/dsa-5151
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.