phpMyAdmin 4.0.0 export.php $GLOBALS memory corruption

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.
8.9$0-$5k0.00

Summaryinfo

A vulnerability identified as critical has been detected in phpMyAdmin 4.0.0. This affects an unknown part of the file export.php. The manipulation of the argument $GLOBALS as part of POST Request leads to memory corruption. This vulnerability is traded as CVE-2013-3241. Furthermore, there is an exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability was found in phpMyAdmin 4.0.0 (Database Administration Software). It has been rated as critical. This issue affects some unknown functionality of the file export.php. The manipulation of the argument $GLOBALS as part of a POST Request leads to a memory corruption vulnerability. Using CWE to declare the problem leads to CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

export.php (aka the export script) in phpMyAdmin 4.x before 4.0.0-rc3 overwrites global variables on the basis of the contents of the POST superglobal array, which allows remote authenticated users to inject values via a crafted request.

The weakness was shared 04/25/2013 by Janek Vind as PMASA-2013-5 as confirmed advisory (Website). The advisory is shared at phpmyadmin.net. The vendor cooperated in the coordination of the public release. The identification of this vulnerability is CVE-2013-3241 since 04/22/2013. The exploitation is known to be difficult. The attack may be initiated remotely. A simple authentication is required for exploitation. Technical details as well as a public exploit are known.

A public exploit has been developed by waraxe and been published immediately after the advisory. The exploit is available at exploit-db.com. It is declared as proof-of-concept. We expect the 0-day to have been worth approximately $25k-$100k. By approaching the search of inurl:export.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 66295 (phpMyAdmin 3.5.x < 3.5.8.1 / 4.x < 4.0.0-rc3 Multiple Vulnerabilities (PMASA-2013-2 - PMASA-2013-5), which helps to determine the existence of the flaw in a target environment. It is assigned to the family CGI abuses.

Upgrading to version 4.0.0-rc3 eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (83794), Exploit-DB (25003), Tenable (66295), SecurityFocus (BID 59461†) and OSVDB (92795†). The entries VDB-8546, VDB-8547 and VDB-8548 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 9.9
VulDB Meta Temp Score: 8.9

VulDB Base Score: 9.9
VulDB Temp Score: 8.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Access: Public
Status: Proof-of-Concept
Author: waraxe
Download: 🔍
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 66295
Nessus Name: phpMyAdmin 3.5.x < 3.5.8.1 / 4.x < 4.0.0-rc3 Multiple Vulnerabilities (PMASA-2013-2 - PMASA-2013-5
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍
Exploit Delay Time: 🔍

Upgrade: phpMyAdmin 4.0.0-rc3

Timelineinfo

04/22/2013 🔍
04/24/2013 +2 days 🔍
04/24/2013 +0 days 🔍
04/25/2013 +1 days 🔍
04/25/2013 +0 days 🔍
04/25/2013 +0 days 🔍
04/25/2013 +0 days 🔍
04/25/2013 +0 days 🔍
05/03/2013 +8 days 🔍
06/18/2014 +411 days 🔍
02/02/2025 +3882 days 🔍

Sourcesinfo

Product: phpmyadmin.net

Advisory: PMASA-2013-5
Researcher: Janek Vind
Status: Confirmed
Confirmation: 🔍
Coordinated: 🔍

CVE: CVE-2013-3241 (🔍)
GCVE (CVE): GCVE-0-2013-3241
GCVE (VulDB): GCVE-100-8549
X-Force: 83794
SecurityFocus: 59461 - phpMyAdmin '$GLOBALS' Array Unauthorized Access Vulnerability
OSVDB: 92795
Vulnerability Center: 45062 - PhpMyAdmin 4.x before 4.0.0-rc3 Remote Security Bypass via a Crafted Request, Medium

scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍

Entryinfo

Created: 05/03/2013 17:03
Updated: 02/02/2025 08:39
Changes: 05/03/2013 17:03 (71), 08/25/2017 09:10 (10), 05/10/2021 10:11 (3), 02/02/2025 08:39 (14)
Complete: 🔍
Committer:
Cache ID: 216::103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Interested in the pricing of exploits?

See the underground prices here!