|
MySQL Query Logging Bypass Security Issue
|
|
Secunia Advisory:
|
SA19034
|
|
|
Release Date:
|
2006-02-27
|
|
Last Update:
|
2006-07-10
|
|
Popularity:
|
13,818 views
|
|
|
Critical:
|
Less critical
|
|
Impact:
|
Security Bypass
|
|
Where:
|
Local system
|
|
Solution Status:
|
Vendor Patch
|
|
| Software: | MySQL 3.x
MySQL 4.x
MySQL 5.x
|
|
|
Secunia CVSS-2 Score:
|
Available in Secunia business solutions 
|
|
|
Subscribe:
|
Instant alerts on relevant vulnerabilities
|
|
| Advisory Content (Page 1 of 3) | [ 1 ] [ 2 ] [ 3 ] | |
|
Description:
1dt.w0lf has discovered a security issue in MySQL, which can be exploited by malicious users to bypass certain security restrictions.
The security issue is caused due to an error within the handling of query logging. This can be exploited to cause part of the query to be incorrectly logged if the query contains the NULL character.
Example:
mysql_query("/*".chr(0)."*/ SELECT * FROM table");
The security issue has been confirmed in version 5.0.18. Other versions may also be affected.
Change Page:
[ 1 ] [ 2 ] [ 3 ]
|
|
|
Track this Secunia Advisory
|
Customers of the Secunia Vulnerability Intelligence solutions will automatically receive updates when new information regarding this advisory is released.
Read more about our Vulnerability Intelligence solutions and what they can do for you and your company.
|
|
|
About this Secunia Advisory
|
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.
|
