-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
x-pack/auditbeat/module/system/socket: defend against exec with zero arguments #30586
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Pinging @elastic/security-external-integrations (Team:Security-External Integrations) |
3350139
to
76e3fda
Compare
Collaborator
76e3fda
to
4a29a34
Compare
…arguments execve can have a zero-length argv so fall back to using /proc/comm, or path base.
4a29a34
to
aa7298f
Compare
adriansr
approved these changes
Feb 28, 2022
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, thanks for fixing
efd6
added a commit
that referenced
this pull request
Mar 1, 2022
…against exec with zero arguments (#30596) * x-pack/auditbeat/module/system/socket: defend against exec with zero arguments (#30586) execve can have a zero-length argv so fall back to using /proc/comm, or path base. (cherry picked from commit 37d07d1) * Update CHANGELOG.next.asciidoc Co-authored-by: Dan Kortschak <90160302+efd6@users.noreply.github.com>
efd6
added a commit
that referenced
this pull request
Mar 1, 2022
… against exec with zero arguments (#30595) * x-pack/auditbeat/module/system/socket: defend against exec with zero arguments (#30586) execve can have a zero-length argv so fall back to using /proc/comm, or path base. (cherry picked from commit 37d07d1) * Update CHANGELOG.next.asciidoc Co-authored-by: Dan Kortschak <90160302+efd6@users.noreply.github.com>
v1v
added a commit
that referenced
this pull request
Mar 2, 2022
…-29710 * '8.1' of github.com:elastic/beats: (51 commits) refactor pushDockerImages (#30414) (#30624) ci: add windows-2022 in the extended meta-stage (#30528) (#30630) Curate k8s testing versions to only keep the actively maintained (#30619) (#30625) [8.1](backport #30355) Add Beats upgrade docs for 8.0 (#30612) Remove references to gcp from the Functionbeat docs (#30579) (#30609) x-pack/auditbeat/module/system/socket: defend against exec with zero arguments (#30586) (#30597) [MySQL Enterprise] Adding default paths values to manifest.yml (#30598) (#30604) metricbeat - fix elasticsearch and kibana integration tests failures in 8.0 (#30566) (#30594) Install gawk as a replacement for mawk in Docker containers. (#30452) (#30465) [Filebeat] Remove RecordedFuture dataset from Threat Intel module (#30564) (#30568) Adjust the documentation of `backoff` options in filestream input (#30552) (#30557) packetbeat/beater: help the GC clean up the Npcap installer if it's not used (#30513) (#30546) Osquerybeat: Add install verification for osquerybeat (#30388) (#30404) Update docker/distribution to 2.8.0 (#30462) (#30540) Add `parsers` examples to `filestream` reference configuration (#30529) (#30537) [8.1](backport #30068) ZooKeeper module: Adapt to ZooKeeper 3.6+ `mntr` response fields' changes. (#30360) [8.1](backport #30512) Switch skip to use `CI` (#30525) Forward-port 8.0.1 changelog to 8.1 (#30517) packetbeat/beater: don't attempt to install npcap when already installed (#30509) (#30511) Add drop and explicit tests to avoid duplicate ingest of elasticsearch logs (#30440) (#30488) ...
# for free
to join this conversation on GitHub.
Already have an account?
# to comment
Labels
8.2-candidate
Auditbeat
backport-7.17
Automated backport to the 7.17 branch with mergify
backport-v8.0.0
Automated backport with mergify
backport-v8.1.0
Automated backport with mergify
bug
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR do?
This change defends against a bounds panic when execve has been called with an argv with zero arguments; exexve can have a zero-length argv so fall back to using /proc/comm, or path base.
Why is it important?
It is possible for a zero argument execve call to result in a bounds check error when attempting to get the process name for the exec'd process, panicking and bringing down the auditbeat process.
Checklist
- [ ] I have made corresponding changes to the documentation- [ ] I have made corresponding change to the default configuration files- [ ] I have added tests that prove my fix is effective or that my feature worksCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
Related issues
Use cases
Screenshots
Logs