First published: Fri Oct 31 2008(Updated: )
The _expand_quoted_text function in libs/Smarty_Compiler.class.php in Smarty 2.6.20 r2797 and earlier allows remote attackers to execute arbitrary PHP code via vectors related to templates and a \ (backslash) before a dollar-sign character.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Smarty | <=2.6.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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2008-4811 has a high severity level due to its ability to allow remote attackers to execute arbitrary PHP code.
To fix CVE-2008-4811, upgrade Smarty to version 2.6.21 or later, which addresses the vulnerability.
CVE-2008-4811 affects multiple versions of Smarty, including all versions prior to 2.6.21.
Yes, CVE-2008-4811 can be exploited remotely without authentication, making it particularly dangerous.
The impact of CVE-2008-4811 includes potential unauthorized access and control of the affected system due to arbitrary PHP code execution.