Smarty up to 3.1.47/4.3.0 cross site scripting

Summaryinfo

A vulnerability has been found in Smarty up to 3.1.47/4.3.0 and classified as problematic. Affected is an unknown function. This manipulation causes cross site scripting. This vulnerability is handled as CVE-2023-28447. The attack can be initiated remotely. There is not any exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability has been found in Smarty up to 3.1.47/4.3.0 (Customer Relationship Management System) and classified as problematic. Affected by this vulnerability is an unknown part. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. As an impact it is known to affect integrity. The summary by CVE is:

Smarty is a template engine for PHP. In affected versions smarty did not properly escape javascript code. An attacker could exploit this vulnerability to execute arbitrary JavaScript code in the context of the user's browser session. This may lead to unauthorized access to sensitive user data, manipulation of the web application's behavior, or unauthorized actions performed on behalf of the user. Users are advised to upgrade to either version 3.1.48 or to 4.3.1 to resolve this issue. There are no known workarounds for this vulnerability.

The weakness was released 03/29/2023 as GHSA-7j98-h7fp-4vwj. It is possible to read the advisory at github.com. This vulnerability is known as CVE-2023-28447 since 03/15/2023. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1059.007 according to MITRE ATT&CK.

The vulnerability scanner Nessus provides a plugin with the ID 211501 (Debian dla-3956 : smarty3 - security update), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 3.1.48 or 4.3.1 eliminates this vulnerability. Applying the patch 685662466f653597428966d75a661073104d713d is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (211501). Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• Customer Relationship Management System

Name

• Smarty

Version

• 3.1.0
• 3.1.1
• 3.1.2
• 3.1.3
• 3.1.4
• 3.1.5
• 3.1.6
• 3.1.7
• 3.1.8
• 3.1.9
• 3.1.10
• 3.1.11
• 3.1.12
• 3.1.13
• 3.1.14
• 3.1.15
• 3.1.16
• 3.1.17
• 3.1.18
• 3.1.19
• 3.1.20
• 3.1.21
• 3.1.22
• 3.1.23
• 3.1.24
• 3.1.25
• 3.1.26
• 3.1.27
• 3.1.28
• 3.1.29
• 3.1.30
• 3.1.31
• 3.1.32
• 3.1.33
• 3.1.34
• 3.1.35
• 3.1.36
• 3.1.37
• 3.1.38
• 3.1.39
• 3.1.40
• 3.1.41
• 3.1.42
• 3.1.43
• 3.1.44
• 3.1.45
• 3.1.46
• 3.1.47
• 4.0
• 4.1
• 4.2
• 4.3.0

License

• commercial

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion