VDB-56325 · CVE-2009-5053 · GCVE-0-2009-5053

Smarty up to 2.6.3 Cache Remote Code Execution

CVSS Meta Temp Score CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.	Current Exploit Price (≈) Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.	CTI Interest Score Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
7.0	$0-$5k	0.00

Summaryinfo

A vulnerability has been found in Smarty up to 2.6.3 and classified as critical. Impacted is an unknown function of the component Cache. Performing a manipulation results in Remote Code Execution. This vulnerability is known as CVE-2009-5053. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as critical, was found in Smarty up to 2.6.3 (Customer Relationship Management System). This affects an unknown part of the component Cache. The manipulation with an unknown input leads to a remote code execution vulnerability. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Unspecified vulnerability in Smarty before 3.0.0 beta 6 allows remote attackers to execute arbitrary PHP code by injecting this code into a cache file.

The weakness was published 02/03/2011 (Website). The advisory is shared at smarty-php.googlecode.com. This vulnerability is uniquely identified as CVE-2009-5053 since 02/03/2011. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 2.6.4 eliminates this vulnerability.

Similar entries are available at VDB-56332, VDB-56331, VDB-56330 and VDB-56329. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Customer Relationship Management System

Name

Smarty

Version

License

commercial

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0

VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Remote Code Execution
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: Smarty 2.6.4

Timelineinfo

02/03/2011 🔍
02/03/2011 +0 days 🔍
02/03/2011 +0 days 🔍
03/20/2015 +1506 days 🔍
02/08/2019 +1421 days 🔍

Sourcesinfo

Advisory: smarty-php.googlecode.com
Status: Not defined
Confirmation: 🔍

CVE: CVE-2009-5053 (🔍)
GCVE (CVE): GCVE-0-2009-5053
GCVE (VulDB): GCVE-100-56325
See also: 🔍

Entryinfo

Created: 03/20/2015 16:16
Updated: 02/08/2019 16:20
Changes: 03/20/2015 16:16 (46), 02/08/2019 16:20 (2)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.