CVE-2013-5000: Infoleak
Published Jul 30, 2013
·Updated
phpMyAdmin 3.5.x before 3.5.8.2 allows remote attackers to obtain sensitive information via an invalid request, which reveals the installation path in an error message, related to config.default.php and other files.
Affected Software
14 affected components
phpMyAdmin phpMyAdmin=3.5.0.0
phpMyAdmin phpMyAdmin=3.5.1.0
phpMyAdmin phpMyAdmin=3.5.2.0
phpMyAdmin phpMyAdmin=3.5.2.1
phpMyAdmin phpMyAdmin=3.5.2.2
phpMyAdmin phpMyAdmin=3.5.3.0
phpMyAdmin phpMyAdmin=3.5.4
phpMyAdmin phpMyAdmin=3.5.5
phpMyAdmin phpMyAdmin=3.5.6
phpMyAdmin phpMyAdmin=3.5.7
phpMyAdmin phpMyAdmin=3.5.7-rc1
phpMyAdmin phpMyAdmin=3.5.8
phpMyAdmin phpMyAdmin=3.5.8-rc1
phpMyAdmin phpMyAdmin=3.5.8.1
Event History
Jul 30, 2013
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description
Frequently Asked Questions
1
What is the severity of CVE-2013-5000?
CVE-2013-5000 is classified as a high severity vulnerability due to its potential to expose sensitive installation paths.
2
How do I fix CVE-2013-5000?
To fix CVE-2013-5000, you should upgrade phpMyAdmin to version 3.5.8.2 or later.
3
Which versions of phpMyAdmin are affected by CVE-2013-5000?
CVE-2013-5000 affects phpMyAdmin versions 3.5.0.0 through 3.5.8.1.
4
What kind of information can attackers obtain through CVE-2013-5000?
Attackers can obtain sensitive information including the installation path and potentially access to configuration files.
5
Is it necessary to update phpMyAdmin if I am using a version prior to 3.5.8.2 in relation to CVE-2013-5000?
Yes, it is crucial to update phpMyAdmin to mitigate the risks associated with CVE-2013-5000.