-
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
winlogbeat 6.6.2 sends utf-16 control codes (carriage return, line feed, tab) #11328
Labels
Comments
adriansr
added a commit
to adriansr/beats
that referenced
this issue
Mar 21, 2019
Previous fix (elastic#11006) made Winlogbeat escape CRLF control characters which are expected in Windows event logs. Fixes elastic#11328
adriansr
added a commit
that referenced
this issue
Mar 21, 2019
adriansr
added a commit
to adriansr/beats
that referenced
this issue
Mar 21, 2019
Previous fix (elastic#11006) made Winlogbeat escape CRLF control characters which are expected in Windows event logs. Fixes elastic#11328 (cherry picked from commit 6865403)
adriansr
added a commit
to adriansr/beats
that referenced
this issue
Mar 21, 2019
Previous fix (elastic#11006) made Winlogbeat escape CRLF control characters which are expected in Windows event logs. Fixes elastic#11328 (cherry picked from commit 6865403)
adriansr
added a commit
to adriansr/beats
that referenced
this issue
Mar 21, 2019
Previous fix (elastic#11006) made Winlogbeat escape CRLF control characters which are expected in Windows event logs. Fixes elastic#11328 (cherry picked from commit 6865403)
adriansr
added a commit
to adriansr/beats
that referenced
this issue
Mar 21, 2019
Previous fix (elastic#11006) made Winlogbeat escape CRLF control characters which are expected in Windows event logs. Fixes elastic#11328 (cherry picked from commit 6865403)
leweafan
pushed a commit
to leweafan/beats
that referenced
this issue
Apr 28, 2023
…ces (elastic#11370) Previous fix (elastic#11006) made Winlogbeat escape CRLF control characters which are expected in Windows event logs. Fixes elastic#11328 (cherry picked from commit 5db0f15)
leweafan
pushed a commit
to leweafan/beats
that referenced
this issue
Apr 28, 2023
…ces (elastic#11372) Previous fix (elastic#11006) made Winlogbeat escape CRLF control characters which are expected in Windows event logs. Fixes elastic#11328 (cherry picked from commit 6865403)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
winlogbeat version 6.6.2 x86_64
OS: Windows 10, Windows Server 2008R2
expected output: for multiline Windows event logs, "message" should have \n or \t
actual output: "message" field contains, e.g.,
"message" => "Special privileges assigned to new logon.\u000d\u000a\u000d\u000aSubject:\u000d\u000a\u0009Security ID:\u0009\u0009S-1-5-18\u000d\u000a\u0009Account Name:\u0009\u0009SYSTEM\u000d\u000a\u0009Account Domain:\u0009\u0009NT AUTHORITY\u000d\u000a\u0009Logon ID:\u0009\u00090x3E7\u000d\u000a\u000d\u000aPrivileges:\u0009\u0009SeAssignPrimaryTokenPrivilege\u000d\u000a\u0009\u0009\u0009SeTcbPrivilege\u000d\u000a\u0009\u0009\u0009SeSecurityPrivilege\u000d\u000a\u0009\u0009\u0009SeTakeOwnershipPrivilege\u000d\u000a\u0009\u0009\u0009SeLoadDriverPrivilege\u000d\u000a\u0009\u0009\u0009SeBackupPrivilege\u000d\u000a\u0009\u0009\u0009SeRestorePrivilege\u000d\u000a\u0009\u0009\u0009SeDebugPrivilege\u000d\u000a\u0009\u0009\u0009SeAuditPrivilege\u000d\u000a\u0009\u0009\u0009SeSystemEnvironmentPrivilege\u000d\u000a\u0009\u0009\u0009SeImpersonatePrivilege\u000d\u000a\u0009\u0009\u0009SeDelegateSessionUserImpersonatePrivilege",
=====================
To reproduce:
download any other version of winlogbeat, unzip, copy to c:\program files\winlogbeat, run install ps1 file. start/stop winlogbeat service to ensure everything works. rename winlogbeat to winlogbeat-.
with service stopped, download 6.6.1, unzip, copy to c:\program files\winlogbeat. copy in winlogbeat.yml. start-service winlogbeat.
=====================
relevant winlogbeat.yml config:
=====================
192.168.1.9 is a logstash 6.6.x instance (tested with 6.6.1 and 6.6.2). logstash config is:
The text was updated successfully, but these errors were encountered: