phpMyAdmin prior 2.1.0 setup.php cross site scripting

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

Summaryinfo

A vulnerability described as problematic has been identified in phpMyAdmin. Affected by this vulnerability is an unknown functionality of the file setup.php. Such manipulation leads to cross site scripting. This vulnerability is listed as CVE-2008-3457. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in phpMyAdmin (Database Administration Software) and classified as problematic. Affected by this issue is an unknown code block of the file setup.php. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. CVE summarizes:

Cross-site scripting (XSS) vulnerability in setup.php in phpMyAdmin before 2.11.8 allows user-assisted remote attackers to inject arbitrary web script or HTML via crafted setup arguments. NOTE: this issue can only be exploited in limited scenarios in which the attacker must be able to modify config/config.inc.php.

The bug was discovered 07/28/2008. The weakness was presented 08/04/2008 by Aung Khant (Website). The advisory is available at redhat.com. This vulnerability is handled as CVE-2008-3457 since 08/04/2008. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1059.007 by the MITRE ATT&CK project.

It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 7 days. During that time the estimated underground price was around $5k-$25k. By approaching the search of inurl:setup.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 34254 (Debian DSA-1641-1 : phpmyadmin - several vulnerabilities), 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.

Upgrading to version 2.1.0 eliminates this vulnerability. A possible mitigation has been published 2 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (44052), Tenable (34254), SecurityFocus (BID 30420†), OSVDB (47487†) and Secunia (SA31263†). See VDB-43537 for similar entry. If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Type

Name

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.3
VulDB Meta Temp Score: 3.9

VulDB Base Score: 4.3
VulDB Temp Score: 3.9
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

NVD Base Score: 🔍

Exploitinginfo

Class: Cross site scripting
CWE: CWE-79 / CWE-94 / CWE-74
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept
Google Hack: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 34254
Nessus Name: Debian DSA-1641-1 : phpmyadmin - several vulnerabilities
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍

OpenVAS ID: 61644
OpenVAS Name: Debian Security Advisory DSA 1641-1 (phpmyadmin)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: phpMyAdmin 2.1.0

Timelineinfo

07/28/2008 🔍
07/28/2008 +0 days 🔍
07/29/2008 +1 days 🔍
08/04/2008 +6 days 🔍
08/04/2008 +0 days 🔍
08/04/2008 +0 days 🔍
09/20/2008 +47 days 🔍
09/23/2008 +3 days 🔍
09/29/2008 +6 days 🔍
03/17/2015 +2360 days 🔍
08/17/2019 +1614 days 🔍

Sourcesinfo

Product: phpmyadmin.net

Advisory: redhat.com
Researcher: Aung Khant
Status: Not defined
Confirmation: 🔍

CVE: CVE-2008-3457 (🔍)
GCVE (CVE): GCVE-0-2008-3457
GCVE (VulDB): GCVE-100-43538

OVAL: 🔍

X-Force: 44052
SecurityFocus: 30420 - phpMyAdmin Multiple Cross-Site Scripting Vulnerabilities
Secunia: 31263
OSVDB: 47487 - CVE-2008-3457 - PhpMyAdmin - Cross-Site Scripting Issue
Vulnerability Center: 19619 - phpMyAdmin Setup.php Cross-Site Scripting (XSS) Vulnerability, Medium
Vupen: ADV-2008-2226

See also: 🔍

Entryinfo

Created: 03/17/2015 12:19
Updated: 08/17/2019 17:53
Changes: 03/17/2015 12:19 (74), 08/17/2019 17:53 (8)
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 ▸

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!