-
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
Fix decode_cef handling of escaped LF and CR #29268
Fix decode_cef handling of escaped LF and CR #29268
Conversation
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
330dd65
to
82c012e
Compare
82c012e
to
2ddc373
Compare
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
Escaped LF and CR were not handled inside of CEF extension value. Those characters are now accepted and replaced with their unescaped equivalents. Fixes elastic#16995
2ddc373
to
046ad0a
Compare
046ad0a
to
520b4c4
Compare
* Fix decode_cef handling of escaped LF and CR Escaped LF and CR were not handled inside of CEF extension value. Those characters are now accepted and replaced with their unescaped equivalents. Replace fgoto with fnext to fix generated Go code that had duplicate 'goto' statements. Fixes #16995 (cherry picked from commit 28d00c7)
* Fix decode_cef handling of escaped LF and CR Escaped LF and CR were not handled inside of CEF extension value. Those characters are now accepted and replaced with their unescaped equivalents. Replace fgoto with fnext to fix generated Go code that had duplicate 'goto' statements. Fixes #16995 (cherry picked from commit 28d00c7)
* Fix decode_cef handling of escaped LF and CR Escaped LF and CR were not handled inside of CEF extension value. Those characters are now accepted and replaced with their unescaped equivalents. Replace fgoto with fnext to fix generated Go code that had duplicate 'goto' statements. Fixes #16995 (cherry picked from commit 28d00c7) Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
* Fix decode_cef handling of escaped LF and CR Escaped LF and CR were not handled inside of CEF extension value. Those characters are now accepted and replaced with their unescaped equivalents. Replace fgoto with fnext to fix generated Go code that had duplicate 'goto' statements. Fixes #16995 (cherry picked from commit 28d00c7) Co-authored-by: Andrew Kroh <andrew.kroh@elastic.co>
What does this PR do?
Escaped LF and CR were not handled inside of CEF extension value.
Those characters are now accepted and replaced with their unescaped
equivalents.
Fixes #16995
Why is it important?
CEF decoding was broken by presence of
\n
or\r
in extension values.Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Related issues