Smarty up to 2.6.3 php.ini 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 categorized as very critical has been discovered in Smarty up to 2.6.3. Affected is an unknown function of the file php.ini. Such manipulation leads to Remote Code Execution. This vulnerability is referenced as CVE-2010-4725. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Smarty up to 2.6.3 (Customer Relationship Management System). It has been rated as very critical. Affected by this issue is an unknown functionality of the file php.ini. The manipulation with an unknown input leads to a remote code execution vulnerability. Impacted is confidentiality, integrity, and availability. CVE summarizes:

Smarty before 3.0.0 RC3 does not properly handle an on value of the asp_tags option in the php.ini file, which has unspecified impact and remote attack vectors.

The weakness was published 02/03/2011 (Website). The advisory is available at smarty-php.googlecode.com. This vulnerability is handled as CVE-2010-4725 since 02/03/2011. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 02/08/2019).

By approaching the search of inurl:php.ini it is possible to find vulnerable targets with Google Hacking.

Upgrading to version 2.6.4 eliminates this vulnerability.

Similar entries are available at VDB-56332, VDB-56331, VDB-56329 and VDB-56328. If you want to get best quality of vulnerability data, you may have to visit VulDB.

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
Google Hack: 🔍

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

Entryinfo

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

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!