CVE-2017-1000480: Code Injection
First published: Wed Jan 03 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.
Credit: cve@mitre.org cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debian/smarty3 | 3.1.33+20180830.1.3a78a21f+selfpack1-1+deb10u1 3.1.33+20180830.1.3a78a21f+selfpack1-1+deb10u2 3.1.39-2+deb11u1 3.1.47-2 3.1.48-1 | |
| composer/smarty/smarty | >=3<3.1.32 | 3.1.32 |
| Smarty | >=3.0.0<3.1.32 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://security-tracker.debian.org/tracker/CVE-2017-1000480
- https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-1000480
- https://anonscm.debian.org/cgit/collab-maint/smarty3.git/commit/?h=debian/jessie/updates&id=ffbfea7545154c48a3692e42d776c2b49fb08c68
- https://anonscm.debian.org/cgit/collab-maint/smarty3.git/commit/?h=debian/wheezy/updates&id=9c69bac107523fd5f28c08efd2d5d706e7bed923
- http://das-netzwerkteam.de
- https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=886460
- https://github.com/smarty-php/smarty/commit/614ad1f8b9b00086efc123e49b7bb8efbfa81b61
- https://github.com/smarty-php/smarty/blob/master/change_log.txt
- https://lists.debian.org/debian-lts-announce/2018/01/msg00023.html
- https://lists.debian.org/debian-lts-announce/2018/02/msg00000.html
- https://www.debian.org/security/2018/dsa-4094
- https://nvd.nist.gov/vuln/detail/CVE-2017-1000480
- https://github.com/advisories/GHSA-9m49-vhwv-422g (Advisory)
Frequently Asked Questions
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.
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.
How do I fix CVE-2017-1000480?
To mitigate CVE-2017-1000480, upgrade Smarty to versions 3.1.33 or later.
What versions are vulnerable to CVE-2017-1000480?
Smarty versions before 3.1.32 are vulnerable to CVE-2017-1000480.
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.
- collector/debian-bugs
- alias/CVE-2017-1000480
- collector/security-tracker-debian
- agent/type
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-9m49-vhwv-422g
- agent/software-canonical-lookup
- agent/severity
- agent/references
- agent/weakness
- agent/description
- agent/author
- agent/softwarecombine
- collector/github-advisory
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/first-publish-date
- agent/event
- agent/trending
- agent/source
- agent/tags
- collector/nvd-cve
- source/NVD
- agent/software-canonical-lookup-request
- collector/nvd-index
- package-manager/debian
- package-manager/composer
- vendor/smarty
- canonical/smarty
- version/smarty/3.0.0