search menu icon-carat-right cmu-wordmark

CERT Coordination Center

Microsoft Windows 2000 Event Viewer contains buffer overflow

Vulnerability Note VU#201704

Original Release Date: 2002-05-24 | Last Revised: 2002-05-24


The Windows 2000 event viewer contains a buffer overflow.


The Microsoft Windows 2000 event viewer contains a buffer overflow that can be exploited when a record written to an event log is examined by the event viewer. Both privileged and unprivileged users can read and write to the system and application logs, but only privileged users and processes can read and write the security log. The buffer overflow occurs in the code used to process and display properties of individual event records. For more information, see

The data needed to run code can be inserted into event logs remotely, but an intruder cannot cause the vulnerability to be triggered without tricking or cooercing someone to examine the particular event log record containing the malicious data.


An intruder who can write to an event log can insert data that will cause a buffer overflow to occur when a user examines the record in the event log. This will allow the execution of arbitrary code with the privileges of the person examining the record.


Apply a patch as described in the Microsoft bulletin.

Vendor Information

Affected   Unknown   Unaffected


Updated:  May 23, 2002



Vendor Statement


Vendor Information

The vendor has not provided us with any further information regarding this vulnerability.


The CERT/CC has no additional comments at this time.

If you have feedback, comments, or additional information about this vulnerability, please send us email.

CVSS Metrics

Group Score Vector
Base N/A N/A
Temporal N/A N/A
Environmental N/A



Our thanks to Microsoft, for the information contained in their bulletin

This document was written by Shawn V. Hernan.

Other Information

CVE IDs: CVE-2001-0147
Severity Metric: 2.53
Date Public: 2001-02-26
Date First Published: 2002-05-24
Date Last Updated: 2002-05-24 00:08 UTC
Document Revision: 2

Sponsored by the Department of Homeland Security Office of Cybersecurity and Communications.