-
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
x-pack/filebeat/input/httpjson: Fix nil pointer deref #37591
x-pack/filebeat/input/httpjson: Fix nil pointer deref #37591
Conversation
This pull request does not have a backport label.
To fixup this pull request, you need to add the backport labels for the needed
|
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
770ab5f
to
6252c15
Compare
💚 Build Succeeded
Expand to view the summary
Build stats
❕ Flaky test reportNo test was executed to be analysed. 🤖 GitHub commentsExpand to view the GitHub comments
To re-run your PR in the CI, just comment with:
|
6252c15
to
07d1199
Compare
💚 Build Succeeded
Expand to view the summary
Build stats
❕ Flaky test reportNo test was executed to be analysed. 🤖 GitHub commentsExpand to view the GitHub comments
To re-run your PR in the CI, just comment with:
|
942c178
to
3b2d817
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@bhapas Sorry, I was a bit quick there and realized after pushing that I wasn't actually covering both Step and While cases (code under test only does While if there's no Step), so I expanded that test. |
❕ Build Aborted
Expand to view the summary
Build stats
Test stats 🧪
Test errors
Expand to view the tests failures
|
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsExpand to view the GitHub comments
To re-run your PR in the CI, just comment with:
|
) For chained requests, setting user and password values for basic authentication via a pointer to a requestFactory struct was done before the struct was initialized, resulting in a nil pointer dereference and runtime panic. Moving it to after the initialization resolved the issue. (cherry picked from commit 0c387c5)
) For chained requests, setting user and password values for basic authentication via a pointer to a requestFactory struct was done before the struct was initialized, resulting in a nil pointer dereference and runtime panic. Moving it to after the initialization resolved the issue. (cherry picked from commit 0c387c5)
) (#37623) For chained requests, setting user and password values for basic authentication via a pointer to a requestFactory struct was done before the struct was initialized, resulting in a nil pointer dereference and runtime panic. Moving it to after the initialization resolved the issue. (cherry picked from commit 0c387c5) Co-authored-by: Chris Berkhout <[email protected]>
) (#37624) For chained requests, setting user and password values for basic authentication via a pointer to a requestFactory struct was done before the struct was initialized, resulting in a nil pointer dereference and runtime panic. Moving it to after the initialization resolved the issue. (cherry picked from commit 0c387c5)
…stic#37591) For chained requests, setting user and password values for basic authentication via a pointer to a requestFactory struct was done before the struct was initialized, resulting in a nil pointer dereference and runtime panic. Moving it to after the initialization resolved the issue.
Proposed commit message
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding changes to the documentationI have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
For manual testing, there's a
filebeat.yml
file below that will trigger the issue. The input fails before any requests are made.Run
./filebeat -c filebeat.yml -v
and check the logs for the error. When the requests are successfully made they can be seen on that webhook's page.Related issues