MediumGHSA-65j5-vpm7-6xp4CVE-2018-16831

Smarty Path Traversal Vulnerability

Published 14 May 2022 · Updated 16 Feb 2024

Affected package

Affected: <3.1.33
Fixed in: 3.1.33

Update to the fixed version for your release line, for example:composer require smarty/smarty:^3.1.33

Details

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

Is GHSA-65j5-vpm7-6xp4 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected smarty/smarty, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisorynvd.nist.gov/vuln/detail/CVE-2018-16831
Linkgithub.com/smarty-php/smarty/issues/486
Linkgithub.com/smarty-php/smarty/commit/f9ca3c63d1250bb56b2bda609dcc9dd81f0065f8
Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/smarty/smarty/CVE-2018-16831.yaml
Packagegithub.com/smarty-php/smarty

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.