First published: Sun Oct 19 2014(Updated: )
Smarty before 3.1.21 allows remote attackers to bypass the secure mode restrictions and execute arbitrary PHP code as demonstrated by "{literal}<{/literal}script language=php>" in a template.
Credit: security@debian.org security@debian.org
Affected Software | Affected Version | How to fix |
---|---|---|
composer/smarty/smarty | <3.1.21 | 3.1.21 |
debian/smarty3 | <=3.1.10-2<=3.0~rc1-1 | |
Smarty | <=3.1.20 | |
Smarty | =1.0 | |
Smarty | =1.0a | |
Smarty | =1.0b | |
Smarty | =1.1.0 | |
Smarty | =1.2.0 | |
Smarty | =1.2.1 | |
Smarty | =1.2.2 | |
Smarty | =1.3.0 | |
Smarty | =1.3.1 | |
Smarty | =1.3.2 | |
Smarty | =1.4.0 | |
Smarty | =1.4.0-b1 | |
Smarty | =1.4.0-b2 | |
Smarty | =1.4.1 | |
Smarty | =1.4.2 | |
Smarty | =1.4.3 | |
Smarty | =1.4.4 | |
Smarty | =1.4.5 | |
Smarty | =1.4.6 | |
Smarty | =1.5.0 | |
Smarty | =1.5.1 | |
Smarty | =1.5.2 | |
Smarty | =2.0.0 | |
Smarty | =2.0.1 | |
Smarty | =2.1.0 | |
Smarty | =2.1.1 | |
Smarty | =2.2.0 | |
Smarty | =2.3.0 | |
Smarty | =2.3.1 | |
Smarty | =2.4.0 | |
Smarty | =2.4.1 | |
Smarty | =2.4.2 | |
Smarty | =2.5.0 | |
Smarty | =2.5.0-rc1 | |
Smarty | =2.5.0-rc2 | |
Smarty | =2.6.0 | |
Smarty | =2.6.0-rc1 | |
Smarty | =2.6.0-rc2 | |
Smarty | =2.6.0-rc3 | |
Smarty | =2.6.1 | |
Smarty | =2.6.2 | |
Smarty | =2.6.3 | |
Smarty | =2.6.4 | |
Smarty | =2.6.5 | |
Smarty | =2.6.6 | |
Smarty | =2.6.7 | |
Smarty | =2.6.9 | |
Smarty | =2.6.10 | |
Smarty | =2.6.11 | |
Smarty | =2.6.12 | |
Smarty | =2.6.13 | |
Smarty | =2.6.14 | |
Smarty | =2.6.15 | |
Smarty | =2.6.16 | |
Smarty | =2.6.17 | |
Smarty | =2.6.18 | |
Smarty | =2.6.20 | |
Smarty | =2.6.22 | |
Smarty | =2.6.24 | |
Smarty | =2.6.25 | |
Smarty | =2.6.26 | |
Smarty | =3.0.0 | |
Smarty | =3.0.0-beta4 | |
Smarty | =3.0.0-beta5 | |
Smarty | =3.0.0-beta6 | |
Smarty | =3.0.0-beta7 | |
Smarty | =3.0.0-beta8 | |
Smarty | =3.0.0-rc1 | |
Smarty | =3.0.0-rc2 | |
Smarty | =3.0.0-rc3 | |
Smarty | =3.0.0-rc4 | |
Smarty | =3.0.1 | |
Smarty | =3.0.2 | |
Smarty | =3.0.3 | |
Smarty | =3.0.4 | |
Smarty | =3.0.5 | |
Smarty | =3.0.6 | |
Smarty | =3.0.7 | |
Smarty | =3.1-rc1 | |
Smarty | =3.1.0 | |
Smarty | =3.1.1 | |
Smarty | =3.1.2 | |
Smarty | =3.1.3 | |
Smarty | =3.1.4 | |
Smarty | =3.1.5 | |
Smarty | =3.1.6 | |
Smarty | =3.1.7 | |
Smarty | =3.1.8 | |
Smarty | =3.1.9 | |
Smarty | =3.1.10 | |
Smarty | =3.1.11 | |
Smarty | =3.1.12 | |
Smarty | =3.1.13 | |
Smarty | =3.1.14 | |
Smarty | =3.1.15 | |
Smarty | =3.1.16 | |
Smarty | =3.1.17 | |
Smarty | =3.1.18 | |
Smarty | =3.1.19 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-8350 has a medium severity rating as it allows remote code execution due to a vulnerability in Smarty before version 3.1.21.
To fix CVE-2014-8350, upgrade Smarty to version 3.1.21 or later.
CVE-2014-8350 affects all Smarty versions before 3.1.21, including several earlier versions like 1.x and 2.x.
Yes, CVE-2014-8350 can be exploited remotely by attackers to execute arbitrary PHP code via crafted templates.
There is no separate patch for CVE-2014-8350; the only solution is to upgrade to the fixed version 3.1.21.