CVE-2017-1000480: Code Injection
Published Jan 3, 2018
·Updated
Smarty 3 before 3.1.32 is vulnerable to a PHP code injection when calling fetch() or display() functions on custom resources that does not sanitize template name.
Affected Software
3 affected componentsFixes available
debian/smarty3
3.1.33+20180830.1.3a78a21f+selfpack1-1+deb10u13.1.33+20180830.1.3a78a21f+selfpack1-1+deb10u23.1.39-2+deb11u13.1.47-23.1.48-1
composer/smarty/smarty>=3<3.1.32
3.1.32
Smarty smarty>=3.0.0<3.1.32
Event History
Jan 3, 2018
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Jan 6, 2018
Data Sourced
10:45 AM
SeverityAffected Software
May 14, 2022
Advisory Published
via GitHub·03:46 AM
Frequently Asked Questions
1
What is the severity of CVE-2017-1000480?
CVE-2017-1000480 is classified as a critical vulnerability due to the potential for PHP code injection.
2
How does CVE-2017-1000480 affect Smarty 3 users?
Users of Smarty 3 prior to version 3.1.32 are at risk of unauthorized PHP code execution when using fetch() or display() functions.
3
How do I fix CVE-2017-1000480?
To mitigate CVE-2017-1000480, upgrade Smarty to versions 3.1.33 or later.
4
What versions are vulnerable to CVE-2017-1000480?
Smarty versions before 3.1.32 are vulnerable to CVE-2017-1000480.
5
Is there a workaround for CVE-2017-1000480 if I cannot upgrade?
It is recommended to sanitize template names when calling fetch() or display() functions to help mitigate the risk if an upgrade is not possible.