CVE-2018-16831: Smarty Path Traversal Vulnerability

CVE-2018-16831 · Severity: low · CVSS 3 · Published 2022-05-14

Smarty Path Traversal Vulnerability

Technologies: smarty/smarty (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2018-16831 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2018-16831 being exploited in the wild.
How severe is CVE-2018-16831?
Low severity, with a CVSS score of 3, published 14 May 2022.
Which products and versions are affected?
smarty/smarty (Packagist) ECOSYSTEM:introduced=0,fixed=3.1.33.
Is there a fix for CVE-2018-16831?
Yes. smarty/smarty (Packagist): upgrade to 3.1.33 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-16831?
Check whether you run smarty/smarty (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • smarty/smarty (Packagist): upgrade to 3.1.33 or later
    composer require smarty/smarty:^3.1.33

Affected products

  • smarty/smarty (Packagist) ECOSYSTEM:introduced=0,fixed=3.1.33

Identifiers

  • CVE-2018-16831
  • GHSA-65j5-vpm7-6xp4

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.