|
MySQL InnoDB Denial of Service Vulnerability
|
|
|
|
|
Secunia Advisory:
|
SA27568
|
|
|
Release Date:
|
2007-11-19
|
|
|
Critical:
|
Less critical
|
|
Impact:
|
DoS
|
|
Where:
|
From local network
|
|
Solution Status:
|
Vendor Workaround
|
|
| Software: | MySQL 4.x
MySQL 5.x
|
| | CVE reference: | CVE-2007-5925 (Secunia mirror)
|
|
|
|
|
|
Description:
A vulnerability has been reported in MySQL, which can be exploited by malicious users to cause a DoS (Denial of Service).
The vulnerability is caused due to an assertion error within the InnoDB engine and can be exploited to crash the database server via certain "CONTAINS" statements.
Successful exploitation requires "ALTER" privileges.
The vulnerability is reported in version 5.1.17, 5.0.44, and 4.1.20. Other versions may also be affected.
Solution:
Grant only trusted users access with "ALTER" privileges to affected systems.
Fixes for MySQL 5.x are reportedly available in the InnoDB repository.
Provided and/or discovered by:
Artem Russakovskii
Original Advisory:
http://bugs.mysql.com/bug.php?id=32125
|
|
|
|
|
Please note: The information that this Secunia Advisory is based on comes from a third party unless stated otherwise.
Secunia collects, validates, and verifies all vulnerability reports issued by security research groups, vendors, and others.
|
|
|
|
27 Related Secunia Security Advisories, displaying 10
|
|
|
1. MySQL MyISAM Table Privilege Check Bypass
|
|
2. MySQL Multiple Vulnerabilities
|
|
3. MySQL Security Issue and Two Vulnerabilities
|
|
4. MySQL System Table Information Overwrite Vulnerability
|
|
5. MySQL Denial of Service Vulnerability and Multiple Security Issues
|
|
6. MySQL IF Query Denial of Service Vulnerability
|
|
7. MySQL Single-Row Subselect and INFORMATION_SCHEMA Denial of Service
|
|
8. MySQL Create Database Bypass and Privilege Escalation
|
|
9. MySQL MERGE Table Privilege Revoke Bypass
|
|
10. MySQL Multibyte Encoding SQL Injection Vulnerability
|
Show all related advisories
|
|
|
Send Feedback to Secunia
|
|
If you have new information regarding this Secunia advisory or a product in our database, please send it to us using either our web form or email us at vuln@secunia.com.
Ideas, suggestions, and other feedback are most welcome.
|
|
|
|
