phpMyAdmin up to 4.6.3/4.4.15.7/4.0.10.16 Database/Table Name sql injection

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

Summaryinfo

A vulnerability was found in phpMyAdmin up to 4.6.3/4.4.15.7/4.0.10.16. It has been classified as critical. This issue affects some unknown processing of the component Database/Table Name Handler. The manipulation leads to sql injection. This vulnerability is listed as CVE-2016-6611. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability, which was classified as critical, has been found in phpMyAdmin up to 4.6.3/4.4.15.7/4.0.10.16 (Database Administration Software). This issue affects an unknown code block of the component Database/Table Name Handler. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in phpMyAdmin. A specially crafted database and/or table name can be used to trigger an SQL injection attack through the export functionality. All 4.6.x versions (prior to 4.6.4), 4.4.x versions (prior to 4.4.15.8), and 4.0.x versions (prior to 4.0.10.17) are affected.

The bug was discovered 08/06/2016. The weakness was presented 12/11/2016 by Emanuel Bronshtein (Website). It is possible to read the advisory at securityfocus.com. The identification of this vulnerability is CVE-2016-6611 since 08/06/2016. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1505 according to MITRE ATT&CK.

The vulnerability was handled as a non-public zero-day exploit for at least 42 days. During that time the estimated underground price was around $5k-$25k. The vulnerability scanner Nessus provides a plugin with the ID 93566 (Debian DLA-626-1 : phpmyadmin security update), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Debian Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 176993 (Debian Security Update for phpmyadmin (DLA 1821-1)).

Upgrading to version 4.6.4, 4.4.15.8 or 4.0.10.17 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 Tenable (93566) and SecurityFocus (BID 94117†). See VDB-94038, VDB-94039, VDB-94041 and VDB-94044 for similar entries. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 8.1
VulDB Meta Temp Score: 7.9

VulDB Base Score: 8.1
VulDB Temp Score: 7.7
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 8.1
NVD Vector: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Sql injection
CWE: CWE-89 / CWE-74 / CWE-707
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

Nessus ID: 93566
Nessus Name: Debian DLA-626-1 : phpmyadmin security update
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 802585
OpenVAS Name: SuSE Update for phpMyAdmin openSUSE-SU-2016:2168-1 (phpMyAdmin)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: phpMyAdmin 4.6.4/4.4.15.8/4.0.10.17

Timelineinfo

07/12/2016 🔍
08/06/2016 +25 days 🔍
08/06/2016 +0 days 🔍
09/17/2016 +42 days 🔍
09/19/2016 +2 days 🔍
12/10/2016 +82 days 🔍
12/11/2016 +1 days 🔍
12/11/2016 +0 days 🔍
10/05/2022 +2124 days 🔍

Sourcesinfo

Product: phpmyadmin.net

Advisory: DLA 1821-1⛔
Researcher: Emanuel Bronshtein
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2016-6611 (🔍)
GCVE (CVE): GCVE-0-2016-6611
GCVE (VulDB): GCVE-100-94043
SecurityFocus: 94117 - phpMyAdmin CVE-2016-6611 SQL-Injection Vulnerability

See also: 🔍

Entryinfo

Created: 12/11/2016 09:12
Updated: 10/05/2022 14:36
Changes: 12/11/2016 09:12 (65), 06/23/2019 10:26 (15), 10/05/2022 14:36 (3)
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 ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!