MySQL 5.0.18 and earlier allows local users to bypass logging mechanisms via SQL queries that contain the NULL character, which are not properly handled by the mysql_real_query function. NOTE: this issue was originally reported for the mysql_query function, but the vendor states that since mysql_query expects a null character, this is not an issue for mysql_query.
Metrics
Affected Vendors & Products
Advisories
Source | ID | Title |
---|---|---|
![]() |
DSA-1071-1 | New MySQL 3.23 packages fix several vulnerabilities |
![]() |
DSA-1073-1 | New MySQL 4.1 packages fix several vulnerabilities |
![]() |
DSA-1079-1 | New MySQL 4.0 packages fix several vulnerabilities |
![]() |
EUVD-2006-0907 | MySQL 5.0.18 and earlier allows local users to bypass logging mechanisms via SQL queries that contain the NULL character, which are not properly handled by the mysql_real_query function. NOTE: this issue was originally reported for the mysql_query function, but the vendor states that since mysql_query expects a null character, this is not an issue for mysql_query. |
![]() |
USN-274-1 | MySQL vulnerability |
![]() |
USN-274-2 | MySQL vulnerability |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.

Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2024-08-07T16:48:56.622Z
Reserved: 2006-02-27T00:00:00
Link: CVE-2006-0903

No data.

Status : Deferred
Published: 2006-02-27T23:02:00.000
Modified: 2025-04-03T01:03:51.193
Link: CVE-2006-0903


No data.