CVE-2006-0903
published 2006-02-27CVE-2006-0903: 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…
PriorityP417medium4.6CVSS 2.0
AVLACLAuNCPIPAP
EXPLOIT
EPSS
1.35%
67.9th percentile
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.
Affected
129 ranges· showing 25
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| mysql | mysql | — | — |
| oracle | mysql | — | — |
| oracle | mysql | — | — |
| oracle | mysql | — | — |
| oracle | mysql | — | — |
| oracle | mysql | — | — |
| oracle | mysql | — | — |
| oracle | mysql | — | — |
| oracle | mysql | — | — |
| oracle | mysql | — | — |
CVSS provenance
nvdv2.04.6MEDIUMAV:L/AC:L/Au:N/C:P/I:P/A:P
vendor_redhat4.6MEDIUM
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Ubuntu
MySQL vulnerability
vendor_ubuntu·2006-05-15
CVE-2006-0903 MySQL vulnerability
Title: MySQL vulnerability
Summary: MySQL vulnerability
USN-274-1 fixed a logging bypass in the MySQL server. Unfortunately it
was determined that the original update was not sufficient to
completely fix the vulnerability, thus another update is necessary. We
apologize for the inconvenience.
For reference, these are the details of the original USN:
A logging bypass was discovered in the MySQL query parser. A local
attacker could exploit this by inserting NUL characters into query
strings (even into comments), which would cause the query to be
logged incompletely.
This only affects you if you enabled the 'log' parameter in the
MySQL configuration.
Instructions: In general, a standard system update will make all the necessary changes.
Ubuntu
MySQL vulnerability
vendor_ubuntu·2006-04-27
CVE-2006-0903 MySQL vulnerability
Title: MySQL vulnerability
Summary: MySQL vulnerability
A logging bypass was discovered in the MySQL query parser. A local
attacker could exploit this by inserting NUL characters into query
strings (even into comments), which would cause the query to be logged
incompletely.
This only affects you if you enabled the 'log' parameter in the MySQL
configuration.
Instructions: In general, a standard system update will make all the necessary changes.
Red Hat
Mysql log file obfuscation
vendor_redhat·2006-02-20·CVSS 4.6
CVE-2006-0903 [MEDIUM] Mysql log file obfuscation
Mysql log file obfuscation
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.
GHSA
GHSA-4qqq-9pg4-j3vh: MySQL 5
ghsa_unreviewed·2022-05-01
CVE-2006-0903 [MEDIUM] GHSA-4qqq-9pg4-j3vh: MySQL 5
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.
No detection rules found.
Bugzilla
CVE-2006-0903 Mysql log file obfuscation
bugzilla·2006-06-14·CVSS 4.6
CVE-2006-0903 [MEDIUM] CVE-2006-0903 Mysql log file obfuscation
CVE-2006-0903 Mysql log file obfuscation
+++ This bug was initially created as a clone of Bug #183260 +++
Mysql log file obfuscation
http://secunia.com/advisories/19034
The following text is from tgl:
Yeah, problem confirmed locally: the query log message is truncated,
060227 11:15:47 6 Connect root@localhost on test
6 Query /* x */ select 2+2
6 Quit
060227 11:16:24 7 Connect root@localhost on test
7 Query /*
7 Quit
The report is perhaps deliberately obscure: you can *not* exploit this
through mysql_query() because it expects a null-terminated string
anyway. But you can exploit it through mysql_real_query() which takes
a pointer and count.
I'd class the severity as pretty low, since all it allows is hiding
some traces of an attack after the attacker has already broken into
the data
Bugzilla
CVE-2006-0903 Mysql multiple vulnerabilities (
bugzilla·2006-04-07·CVSS 4.6
CVE-2006-0903 [MEDIUM] CVE-2006-0903 Mysql multiple vulnerabilities (
CVE-2006-0903 Mysql multiple vulnerabilities (
+++ This bug was initially created as a clone of Bug #183261 +++
Mysql log file obfuscation
http://secunia.com/advisories/19034
The following text is from tgl:
Yeah, problem confirmed locally: the query log message is truncated,
060227 11:15:47 6 Connect root@localhost on test
6 Query /* x */ select 2+2
6 Quit
060227 11:16:24 7 Connect root@localhost on test
7 Query /*
7 Quit
The report is perhaps deliberately obscure: you can *not* exploit this
through mysql_query() because it expects a null-terminated string
anyway. But you can exploit it through mysql_real_query() which takes
a pointer and count.
I'd class the severity as pretty low, since all it allows is hiding
some traces of an attack after the attacker has already broken into
th
Bugzilla
CVE-2006-0903 Mysql log file obfuscation
bugzilla·2006-02-27·CVSS 4.6
CVE-2006-0903 [MEDIUM] CVE-2006-0903 Mysql log file obfuscation
CVE-2006-0903 Mysql log file obfuscation
Mysql log file obfuscation
http://secunia.com/advisories/19034
The following text is from tgl:
Yeah, problem confirmed locally: the query log message is truncated,
060227 11:15:47 6 Connect root@localhost on test
6 Query /* x */ select 2+2
6 Quit
060227 11:16:24 7 Connect root@localhost on test
7 Query /*
7 Quit
The report is perhaps deliberately obscure: you can *not* exploit this
through mysql_query() because it expects a null-terminated string
anyway. But you can exploit it through mysql_real_query() which takes
a pointer and count.
I'd class the severity as pretty low, since all it allows is hiding
some traces of an attack after the attacker has already broken into
the database. But since MySQL make a point of how mysql_real_query()
suppo
Bugzilla
CVE-2006-0903 Mysql log file obfuscation
bugzilla·2006-02-27·CVSS 4.6
CVE-2006-0903 [MEDIUM] CVE-2006-0903 Mysql log file obfuscation
CVE-2006-0903 Mysql log file obfuscation
Mysql log file obfuscation
http://secunia.com/advisories/19034
The following text is from tgl:
Yeah, problem confirmed locally: the query log message is truncated,
060227 11:15:47 6 Connect root@localhost on test
6 Query /* x */ select 2+2
6 Quit
060227 11:16:24 7 Connect root@localhost on test
7 Query /*
7 Quit
The report is perhaps deliberately obscure: you can *not* exploit this
through mysql_query() because it expects a null-terminated string
anyway. But you can exploit it through mysql_real_query() which takes
a pointer and count.
I'd class the severity as pretty low, since all it allows is hiding
some traces of an attack after the attacker has already broken into
the database. But since MySQL make a point of how mysql_real_query()
suppo
http://archives.neohapsis.com/archives/fulldisclosure/2006-02/0653.htmlhttp://bugs.mysql.com/bug.php?id=17667http://rst.void.ru/papers/advisory39.txthttp://secunia.com/advisories/19034http://secunia.com/advisories/19502http://secunia.com/advisories/19814http://secunia.com/advisories/20241http://secunia.com/advisories/20253http://secunia.com/advisories/20333http://secunia.com/advisories/20625http://secunia.com/advisories/30351http://securitytracker.com/id?1015693http://www.debian.org/security/2006/dsa-1071http://www.debian.org/security/2006/dsa-1073http://www.debian.org/security/2006/dsa-1079http://www.mandriva.com/security/advisories?name=MDKSA-2006:064http://www.redhat.com/support/errata/RHSA-2006-0544.htmlhttp://www.redhat.com/support/errata/RHSA-2007-0083.htmlhttp://www.redhat.com/support/errata/RHSA-2008-0364.htmlhttp://www.securityfocus.com/bid/16850http://www.ubuntu.com/usn/usn-274-2http://www.vupen.com/english/advisories/2006/0752https://exchange.xforce.ibmcloud.com/vulnerabilities/24966https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9915https://usn.ubuntu.com/274-1/http://archives.neohapsis.com/archives/fulldisclosure/2006-02/0653.htmlhttp://bugs.mysql.com/bug.php?id=17667http://rst.void.ru/papers/advisory39.txthttp://secunia.com/advisories/19034http://secunia.com/advisories/19502http://secunia.com/advisories/19814http://secunia.com/advisories/20241http://secunia.com/advisories/20253http://secunia.com/advisories/20333http://secunia.com/advisories/20625http://secunia.com/advisories/30351http://securitytracker.com/id?1015693http://www.debian.org/security/2006/dsa-1071http://www.debian.org/security/2006/dsa-1073http://www.debian.org/security/2006/dsa-1079http://www.mandriva.com/security/advisories?name=MDKSA-2006:064http://www.redhat.com/support/errata/RHSA-2006-0544.htmlhttp://www.redhat.com/support/errata/RHSA-2007-0083.htmlhttp://www.redhat.com/support/errata/RHSA-2008-0364.htmlhttp://www.securityfocus.com/bid/16850http://www.ubuntu.com/usn/usn-274-2http://www.vupen.com/english/advisories/2006/0752https://exchange.xforce.ibmcloud.com/vulnerabilities/24966https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A9915https://usn.ubuntu.com/274-1/
2006-02-27
Published