Alerts This Week
Warning Icon 1 714
Alerts This Week
Warning Icon 1 714

Gentoo: GLSA-202105-06 Normal: Smarty Remote Code Execution Threats

gentoo
Calendar Grey May 26, 2021
Dist Gentoo Esm H88
A recent Gentoo security advisory warns of critical vulnerabilities in the Smarty template engine, risking code execution and data exposure for web apps that utilize it.
Multiple vulnerabilities in the Smarty template engine might allow remote attackers to execute arbitrary PHP code.

Summary

Multiple vulnerabilities have been discovered in Smarty template engine. Please review the CVE identifiers referenced below for details.

Resolution

All Smarty template engine users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-php/smarty-3.1.39"

References

[ 1 ] CVE-2021-26119 https://nvd.nist.gov/vuln/detail/CVE-2021-26119 [ 2 ] CVE-2021-26120 https://nvd.nist.gov/vuln/detail/CVE-2021-26120

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/202105-06
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: Normal
Title: Smarty: Multiple vulnerabilities
Date: May 26, 2021
Bugs: #772206
ID: 202105-06

Synopsis

Multiple vulnerabilities in the Smarty template engine might allow remote attackers to execute arbitrary PHP code.

Background

Smarty is a template engine for PHP.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-php/smarty < 3.1.39 >= 3.1.39

Impact

===== Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

Your message here