Bug 183261

Summary:	CVE-2006-0903 Mysql log file obfuscation
Product:	[Fedora] Fedora	Reporter:	Josh Bressers <bressers>
Component:	mysql	Assignee:	Tom Lane <tgl>
Status:	CLOSED RAWHIDE	QA Contact:	David Lawrence <dkl>
Severity:	low	Docs Contact:
Priority:	low
Version:	4	CC:	byte, hhorak
Target Milestone:	---	Keywords:	Security
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:	source=secunia,reported=20060227,impact=low,public=20060220
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-05-18 01:51:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	194613

Description Josh Bressers 2006-02-27 20:15:29 UTC

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()
supports embedded nulls in the query string, it's certainly a bug.


This issue also affects FC3

Comment 1 Josh Bressers 2006-02-27 20:20:11 UTC

attachment 125344 [details] is a testcase from tgl:

    I've attached a test case.	Start the server with query logging enabled
    (easiest way is to modify the init script to add "--log" to the
    mysqld_safe command line), run program, look at log file.

Comment 3 Tom Lane 2006-05-18 01:51:26 UTC

This is fixed by upstream changes in 4.1.19.