phpMyAdmin up to 4.6.3/4.4.15.7/4.0.10.16 information disclosure

HistoryDiffrelatejsonxmlCTI

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.
5.2	$0-$5k	0.00

Summaryinfo

A vulnerability was found in phpMyAdmin up to 4.6.3/4.4.15.7/4.0.10.16. It has been rated as critical. The affected element is an unknown function. This manipulation causes information disclosure. This vulnerability is registered as CVE-2016-6613. Remote exploitation of the attack is possible. No exploit is available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability has been found in phpMyAdmin up to 4.6.3/4.4.15.7/4.0.10.16 (Database Administration Software) and classified as critical. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

An issue was discovered in phpMyAdmin. A user can specially craft a symlink on disk, to a file which phpMyAdmin is permitted to read but the user is not, which phpMyAdmin will then expose to the user. 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 published 12/11/2016 by Emanuel Bronshtein (Website). The advisory is shared at securityfocus.com. This vulnerability is known as CVE-2016-6613 since 08/06/2016. The attack can be launched remotely. The successful exploitation requires a single authentication. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1592 for this issue.

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 94115†). Similar entries are available at VDB-94038, VDB-94039, VDB-94041 and VDB-94043. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Database Administration Software

Name

phpMyAdmin

Version

License

open-source

Website

Product: https://www.phpmyadmin.net/

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.2

VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.3
NVD Vector: 🔍

CVSSv2info

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

Exploitinginfo

Class: Information disclosure
CWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

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-6613 (🔍)
GCVE (CVE): GCVE-0-2016-6613
GCVE (VulDB): GCVE-100-94045
SecurityFocus: 94115 - phpMyAdmin CVE-2016-6613 Local Information Disclosure Vulnerability

See also: 🔍

Entryinfo

Created: 12/11/2016 09:12
Updated: 10/05/2022 14:42
Changes: 12/11/2016 09:12 (64), 06/23/2019 10:41 (15), 10/05/2022 14:42 (4)
Complete: 🔍
Cache ID: 216:101:103

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