First published: Thu Apr 26 2018(Updated: )
`Smarty_Security::isTrustedResourceDir()` in Smarty before 3.1.33 is prone to a path traversal vulnerability due to insufficient template code sanitization. This allows attackers controlling the executed template code to bypass the trusted directory security restriction and read arbitrary files.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
composer/smarty/smarty | <3.1.33 | |
composer/smarty/smarty | <3.1.33 | 3.1.33 |
Smarty | <3.1.33 | |
Debian | =9.0 |
https://github.com/sbaresearch/advisories/tree/public/2018/SBA-ADV-20180420-01_Smarty_Path_Traversal
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2018-13982 is classified as a high severity vulnerability due to its potential for arbitrary file access.
To fix CVE-2018-13982, upgrade Smarty to version 3.1.33 or later.
CVE-2018-13982 can be exploited for path traversal attacks allowing attackers to read sensitive files on the server.
Smarty versions prior to 3.1.33 are affected by CVE-2018-13982.
The impact of CVE-2018-13982 includes potential unauthorized access to sensitive files, leading to data breaches.