October 7, 2019
vbulletin is prone to multiple SQL-injection vulnerabilities because it fails to properly sanitize user-supplied input before using it in an SQL query. An attacker can leverage these issues to compromise the application, access or modify data, or exploit latent vulnerabilities in the underlying database. vBulletin 5.5.4 and prior versions are vulnerable.
- VBulletin VBulletin 5.0.1
- VBulletin VBulletin 5.0.2
- VBulletin VBulletin 5.0.4
- VBulletin VBulletin 5.0.5
- VBulletin VBulletin 5.1.0
- VBulletin VBulletin 5.1.1
- VBulletin VBulletin 5.1.4
- VBulletin VBulletin 5.1.5
- VBulletin VBulletin 5.1.6
- VBulletin VBulletin 5.1.7
- VBulletin VBulletin 5.1.8
- VBulletin VBulletin 5.1.9
- VBulletin VBulletin 5.2.2
- VBulletin VBulletin 5.3.0
- VBulletin VBulletin 5.4.0
- VBulletin VBulletin 5.5.0
- VBulletin VBulletin 5.5.2
- VBulletin VBulletin 5.5.3
- VBulletin VBulletin 5.5.4
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.
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.
Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to detect and block attacks and anomalous activity such as requests containing suspicious URI sequences. Since the webserver may log such requests, review logs regularly.
Modify default ACL settings.
Implement database access control to limit the immediate impact of such vulnerabilities on the data within the database and possibly the database itself. Ensure that applications are isolated from one another and from sensitive data in the database through separate user accounts and restrictive ACL configurations.
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.