phpMyAdmin up to 4.0.10.15/4.4.15.6/4.6.2 preg_replace code injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 9.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in phpMyAdmin up to 4.0.10.15/4.4.15.6/4.6.2. Affected by this issue is some unknown functionality of the component preg_replace Handler. This manipulation causes code injection. This vulnerability appears as CVE-2016-5734. The attack may be initiated remotely. In addition, an exploit is available. You should upgrade the affected component.
Details
A vulnerability has been found in phpMyAdmin up to 4.0.10.15/4.4.15.6/4.6.2 (Database Administration Software) and classified as very critical. Affected by this vulnerability is some unknown functionality of the component preg_replace Handler. The manipulation with an unknown input leads to a code injection vulnerability. The CWE definition for the vulnerability is CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
phpMyAdmin 4.0.x before 4.0.10.16, 4.4.x before 4.4.15.7, and 4.6.x before 4.6.3 does not properly choose delimiters to prevent use of the preg_replace e (aka eval) modifier, which might allow remote attackers to execute arbitrary PHP code via a crafted string, as demonstrated by the table search-and-replace implementation.
The weakness was presented 07/03/2016 with Cure53 (Website). The advisory is shared at phpmyadmin.net. This vulnerability is known as CVE-2016-5734 since 06/21/2016. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 02/01/2025). MITRE ATT&CK project uses the attack technique T1059 for this issue.
It is possible to download the exploit at exploit-db.com. It is declared as highly functional. We expect the 0-day to have been worth approximately $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 91939 (FreeBSD : phpMyAdmin -- multiple vulnerabilities (e7028e1d-3f9b-11e6-81f9-6805ca0b3d42)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 11677 (phpMyAdmin Multiple Security Vulnerabilities (PMASA-2016-27, PMASA-2016-23)).
Upgrading to version 4.0.10.16, 4.4.15.7 or 4.6.3 eliminates this vulnerability. A possible mitigation has been published even before and not after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at Exploit-DB (40185), Tenable (91939) and SecurityFocus (BID 91387†). See VDB-88563, VDB-88565, VDB-88569 and VDB-88571 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 4.0.10.0
- 4.0.10.1
- 4.0.10.2
- 4.0.10.3
- 4.0.10.4
- 4.0.10.5
- 4.0.10.6
- 4.0.10.7
- 4.0.10.8
- 4.0.10.9
- 4.0.10.10
- 4.0.10.11
- 4.0.10.12
- 4.0.10.13
- 4.0.10.14
- 4.0.10.15
- 4.4.15.0
- 4.4.15.1
- 4.4.15.2
- 4.4.15.3
- 4.4.15.4
- 4.4.15.5
- 4.4.15.6
- 4.6.0
- 4.6.1
- 4.6.2
License
Website
- Product: https://www.phpmyadmin.net/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 9.8VulDB Meta Temp Score: 9.6
VulDB Base Score: 9.8
VulDB Temp Score: 9.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
NVD Vector: 🔍
CVSSv2
| 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: 🔍
Exploiting
Class: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Highly functional
Download: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 91939
Nessus Name: FreeBSD : phpMyAdmin -- multiple vulnerabilities (e7028e1d-3f9b-11e6-81f9-6805ca0b3d42)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
OpenVAS ID: 69121
OpenVAS Name: Fedora Update for phpMyAdmin FEDORA-2016-81c2dabf20
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
MetaSploit ID: phpmyadmin_null_termination_exec.rb
MetaSploit Name: phpMyAdmin Authenticated Remote Code Execution
MetaSploit File: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: phpMyAdmin 4.0.10.16/4.4.15.7/4.6.3
Patch: github.com
Timeline
06/21/2016 🔍06/23/2016 🔍
07/01/2016 🔍
07/02/2016 🔍
07/03/2016 🔍
07/04/2016 🔍
07/05/2016 🔍
02/01/2025 🔍
Sources
Product: phpmyadmin.netAdvisory: 1cc7466db3a05e95fe57a6702f41773e6829d54b
Organization: Cure53
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2016-5734 (🔍)
GCVE (CVE): GCVE-0-2016-5734
GCVE (VulDB): GCVE-100-88573
SecurityFocus: 91387 - phpMyAdmin CVE-2016-5734 Multiple Arbitrary PHP Code Execution Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 07/04/2016 10:10Updated: 02/01/2025 23:15
Changes: 07/04/2016 10:10 (68), 02/15/2019 16:41 (17), 08/26/2022 13:11 (4), 02/01/2025 23:15 (16)
Complete: 🔍
Cache ID: 216:844:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.