CVE-2018-16831 : Smarty before 3.1.33-dev-4 allows attackers to bypass the trusted

Smarty before 3.1.33-dev-4 allows attackers to bypass the trusted_dir protection mechanism via a file:./../ substring in an include statement.

Published 2018-09-11 13:29:01

Updated 2018-11-16 14:38:58

Source MITRE

View at NVD, CVE.org

Vulnerability category: Directory traversal

Products affected by CVE-2018-16831

Smarty » Smarty
Versions from including (>=) 3.0.0 and up to, including, (<=) 3.1.32
cpe:2.3:a:smarty:smarty:*:*:*:*:*:*:*:*
Matching versions

EPSS FAQ

0.32%

Probability of exploitation activity in the next 30 days EPSS Score History

~ 70 %

Percentile, the proportion of vulnerabilities that are scored at or less

Base Score	Base Severity	CVSS Vector	Exploitability Score	Impact Score	Score Source
7.1	HIGH	AV:N/AC:M/Au:N/C:C/I:N/A:N	8.6	6.9	NIST
Access Vector: Network Access Complexity: Medium Authentication: None Confidentiality Impact: Complete Integrity Impact: None Availability Impact: None
5.9	MEDIUM	CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N	2.2	3.6	NIST
Attack Vector: Network Attack Complexity: High Privileges Required: None User Interaction: None Scope: Unchanged Confidentiality: High Integrity: None Availability: None

CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Assigned by: nvd@nist.gov (Primary)

https://github.com/smarty-php/smarty/issues/486

even you enable secrity .trusted_dir can be bypassed · Issue #486 · smarty-php/smarty · GitHub
Exploit;Third Party Advisory

Jump to