Smarty up to 2.6.3 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.
9.4$0-$5k0.00

Summaryinfo

A vulnerability identified as very critical has been detected in Smarty up to 2.6.3. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in Remote Code Execution. This vulnerability is identified as CVE-2010-4726. There is not any exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as very critical has been found in Smarty up to 2.6.3 (Customer Relationship Management System). This affects some unknown functionality. 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 the math plugin in Smarty before 3.0.0 RC1 has unknown impact and remote attack vectors. NOTE: this might overlap CVE-2009-1669.

The weakness was released 02/03/2011 (Website). It is possible to read the advisory at smarty-php.googlecode.com. This vulnerability is uniquely identified as CVE-2010-4726 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. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/08/2019).

Upgrading to version 2.6.4 eliminates this vulnerability.

Entries connected to this vulnerability are available at VDB-56332, VDB-56330, VDB-56329 and VDB-56328. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.8
VulDB Meta Temp Score: 9.4

VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

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-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

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-2010-4726 (🔍)
GCVE (CVE): GCVE-0-2010-4726
GCVE (VulDB): GCVE-100-56331
See also: 🔍

Entryinfo

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

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!