-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad event log records can cause Winlogbeat crashes in XP / 2003 #6234
Labels
Comments
adriansr
added a commit
to adriansr/beats
that referenced
this issue
Jan 31, 2018
There was a crash in the eventlogging module used in legacy Windows versions (XP and 2003 server). It is necessary to account for the case where an event contains fewer parameters than required by its format string. Closes elastic#6234
adriansr
added a commit
to adriansr/beats
that referenced
this issue
Jan 31, 2018
There was a crash in the eventlogging module used in legacy Windows versions (XP and 2003 server). It is necessary to account for the case where an event contains fewer parameters than required by its format string. Closes elastic#6234
andrewkroh
pushed a commit
that referenced
this issue
Feb 8, 2018
There was a crash in the eventlogging module used in legacy Windows versions (XP and 2003 server). It is necessary to account for the case where an event contains fewer parameters than required by its format string. Closes #6234
adriansr
added a commit
to adriansr/beats
that referenced
this issue
Feb 12, 2018
There was a crash in the eventlogging module used in legacy Windows versions (XP and 2003 server). It is necessary to account for the case where an event contains fewer parameters than required by its format string. Closes elastic#6234
andrewkroh
pushed a commit
that referenced
this issue
Feb 13, 2018
* Winlogbeat: Fix event formatting with missing params There was a crash in the eventlogging module used in legacy Windows versions (XP and 2003 server). It is necessary to account for the case where an event contains fewer parameters than required by its format string. Closes #6234
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If an event is published to the Windows event log that contains fewer message parameters than are required by the message template this will cause a crash.
FormatMessage
does not safely check the number of arguments provided against the number required by the template.For example:
["akroh", "192.168.0.1"]
.User %1 connected from %2:%3.
.FormatMessage
causes a STATUS_ACCESS_VIOLATION exception that crashes Winlogbeat.For confirmed bugs, please report:
The text was updated successfully, but these errors were encountered: