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

There are packages installed that are affected by a vulnerability referenced in the following CVE:

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

The remote Ubuntu 18.04 LTS host has a package installed that is affected by multiple vulnerabilities as referenced in the USN-5348-1 advisory.

    David Gnedt and Thomas Konrad discovered that Smarty was incorrectly sanitizing the paths present in the     templates. An attacker could possibly use this use to read arbitrary files when controlling the executed     template. (CVE-2018-13982)

    It was discovered that Smarty was incorrectly sanitizing the paths present in the templates. An attacker     could possibly use this use to read arbitrary files when controlling the executed template.
    (CVE-2018-16831)

    It was discovered that Smarty was incorrectly validating security policy data, allowing the execution of     static classes even when not permitted by the security settings. An attacker could possibly use this issue     to execute arbitrary code. (CVE-2021-21408)

    It was discovered that Smarty was incorrectly managing access control to template objects, which allowed     users to perform a sandbox escape. An attacker could possibly use this issue to send specially crafted     input to applications that use Smarty and execute arbitrary code. (CVE-2021-26119)

    It was discovered that Smarty was not checking for special characters when setting function names during     plugin compile operations. An attacker could possibly use this issue to send specially crafted input to     applications that use Smarty and execute arbitrary code. (CVE-2021-26120)

    It was discovered that Smarty was incorrectly sanitizing characters in math strings processed by the math     function. An attacker could possibly use this issue to send specially crafted input to applications that     use Smarty and execute arbitrary code. (CVE-2021-29454)

Tenable has extracted the preceding description block directly from the Ubuntu security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

===== 3.1.33 release ===== 12.09.2018

===== 3.1.33-dev-12 =====

03.09.2018

  - bugfix {foreach} using new style property access like     {$item@property} on Smarty 2 style named foreach loop     could produce errors     https://github.com/smarty-php/smarty/issues/484

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora update system website.
Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

ID	Name	Product	Family	Type	Severity
434491	SCA: security update for smarty/smarty (GHSA-65j5-vpm7-6xp4)	Tenable Cloud Security	SCA Checks	Local	medium
434491	SCA: security update for smarty/smarty (GHSA-65j5-vpm7-6xp4)	Tenable Self-Hosted Container Security	SCA Checks	Local	medium
159268	Ubuntu 18.04 LTS : Smarty vulnerabilities (USN-5348-1)	Nessus	Ubuntu Local Security Checks	Local	critical
122684	Fedora 29 : php-Smarty (2019-e595e8a7d7)	Nessus	Fedora Local Security Checks	Local	critical
122683	Fedora 28 : php-Smarty (2019-d248c5aa39)	Nessus	Fedora Local Security Checks	Local	critical

Detections

Analytics

CVE-2018-16831

medium

Tenable Plugins

medium

medium

critical

critical

critical