Arbitrary Code Injection Affecting smarty3 package, versions <3.1.31+20161214.1.c7d42e4+selfpack1-3
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-DEBIAN11-SMARTY3-528762
- published3 Jan 2018
- disclosed3 Jan 2018
Introduced: 3 Jan 2018
CVE-2017-1000480 (opens in a new tab)How to fix?
Upgrade Debian:11 smarty3 to version 3.1.31+20161214.1.c7d42e4+selfpack1-3 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream smarty3 package and not the smarty3 package as distributed by Debian.
See How to fix? for Debian:11 relevant fixed versions and status.
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.
References
- https://security-tracker.debian.org/tracker/CVE-2017-1000480
- https://www.debian.org/security/2018/dsa-4094
- https://lists.debian.org/debian-lts-announce/2018/01/msg00023.html
- https://lists.debian.org/debian-lts-announce/2018/02/msg00000.html
- https://github.com/smarty-php/smarty/blob/master/change_log.txt
- http://people.ubuntu.com/~ubuntu-security/cve/CVE-2017-1000480