First published: Tue 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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
PhpMyAdmin | =3.5.0.0 | |
PhpMyAdmin | =3.5.1.0 | |
PhpMyAdmin | =3.5.2.0 | |
PhpMyAdmin | =3.5.2.1 | |
PhpMyAdmin | =3.5.2.2 | |
PhpMyAdmin | =3.5.3.0 | |
PhpMyAdmin | =3.5.4 | |
PhpMyAdmin | =3.5.5 | |
PhpMyAdmin | =3.5.6 | |
PhpMyAdmin | =3.5.7 | |
PhpMyAdmin | =3.5.7-rc1 | |
PhpMyAdmin | =3.5.8 | |
PhpMyAdmin | =3.5.8-rc1 | |
PhpMyAdmin | =3.5.8.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2013-5000 is classified as a high severity vulnerability due to its potential to expose sensitive installation paths.
To fix CVE-2013-5000, you should upgrade phpMyAdmin to version 3.5.8.2 or later.
CVE-2013-5000 affects phpMyAdmin versions 3.5.0.0 through 3.5.8.1.
Attackers can obtain sensitive information including the installation path and potentially access to configuration files.
Yes, it is crucial to update phpMyAdmin to mitigate the risks associated with CVE-2013-5000.