October 28, 2019
phpMyAdmin is prone to an SQL-injection vulnerability because it fails to properly sanitize user-supplied input before using it in an SQL query. Exploiting this issue could allow an attacker to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database. phpMyAdmin versions prior to 4.9.2 are vulnerable.
- phpMyAdmin phpMyAdmin 4.7.7
- phpMyAdmin phpMyAdmin 4.7.8
- phpMyAdmin phpMyAdmin 4.8.0
- phpMyAdmin phpMyAdmin 4.8.1
- phpMyAdmin phpMyAdmin 4.8.2
- phpMyAdmin phpMyAdmin 4.8.3
- phpMyAdmin phpMyAdmin 4.8.4
- phpMyAdmin phpMyAdmin 4.8.5
- phpMyAdmin phpMyAdmin 4.8.6
- phpMyAdmin phpMyAdmin 4.9.0
- phpMyAdmin phpMyAdmin 4.9.1
Block external access at the network boundary, unless external parties require service.
Filter access to the affected computer at the network boundary if global access isn't needed. Restricting access to only trusted computers and networks might greatly reduce the likelihood of a successful exploit.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
NIDS may identify and block generic attacks against web applications. Detecting and filtering SQL statements may reduce the likelihood of successful exploits.
Modify default ACL settings.
Implement database access control to limit the immediate impact of such vulnerabilities on the data and possibly the database itself. Ensure that applications are isolated from one another and from sensitive data through separate user accounts and restrictive ACL configurations.
Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of latent vulnerabilities, always run nonadministrative software as an unprivileged user with minimal access rights.
Updates are available. Please see the references or vendor advisory for more information.
© 1995- Symantec Corporation
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from email@example.com.
The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Security Response, and firstname.lastname@example.org are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.