bugtraq
[Top] [All Lists]

Re: [Full-disclosure] Fun with event logs (semi-offtopic)

To: full-disclosure@lists.grok.org.uk, bugtraq@securityfocus.com
Subject: Re: [Full-disclosure] Fun with event logs (semi-offtopic)
From: endrazine <endrazine@gmail.com>
Date: Thu, 21 Dec 2006 14:09:43 +0100
Delivered-to: sp-com-lists@consult.net
Delivered-to: bugtraq-list@securepoint.com
Delivered-to: mailing list bugtraq@securityfocus.com
Delivered-to: moderator for bugtraq@securityfocus.com
In-reply-to: <169373868.20061221152209@SECURITY.NNOV.RU>
List-help: <mailto:bugtraq-help@securityfocus.com>
List-id: <bugtraq.list-id.securityfocus.com>
List-post: <mailto:bugtraq@securityfocus.com>
List-subscribe: <mailto:bugtraq-subscribe@securityfocus.com>
List-unsubscribe: <mailto:bugtraq-unsubscribe@securityfocus.com>
Mailing-list: contact bugtraq-help@securityfocus.com; run by ezmlm
References: <169373868.20061221152209@SECURITY.NNOV.RU>
User-agent: Thunderbird 1.5.0.7 (X11/20061025)
Heya lists & 3APA3A,

3APA3A a écrit :
Dear full-disclosure@lists.grok.org.uk,

There  is  interesting  thing  with  event  logging on Windows. The only
security  aspect  of  it  is  event log record tampering and performance
degradation,  but  it may become sensitive is some 3rd party software is
used for automated event log analysis.

The   problem   is   a  kind  of  "Format  string"  vulnerability  where
user-supplied  input  is  used  for  event log record. For ReportEvent()
function  %1,  %2,  etc  have  a  special  meaning and are replaced with
corresponding string from lpStrings.
It looks more like a variable replacement (like $0 $1 ... in bash shell) than a format string issue to me.
And it seems indeed to be a relevant information disclosure bug.


Cheers,

endrazine-

<Prev in Thread] Current Thread [Next in Thread>