-
Notifications
You must be signed in to change notification settings - Fork 4
Fix crash in execve filename parameter parsing #98
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
Open
Stringy
wants to merge
1
commit into
0.23.1-stackrox
Choose a base branch
from
giles/fix-execve-filename-crash
base: 0.23.1-stackrox
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
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.
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.
🎯 Functional Correctness | 🟠 Major | ⚡ Quick win
Update
invalid_string_lenfor the new contract.userspace/libsinsp/test/events_param.ut.cppLines 515-539 corrupt an embedded NUL and expectadvance_ts_get_eventto throw. This branch now accepts that mismatch, so the test still asserts the removed exception path. Change it to assert successful processing. Add a separate test for missing terminators or zero recorded lengths if those inputs remain invalid.🤖 Prompt for AI Agents
🩺 Stability & Availability | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: stackrox/falcosecurity-libs
Length of output: 9343
🏁 Script executed:
Repository: stackrox/falcosecurity-libs
Length of output: 50383
🏁 Script executed:
Repository: stackrox/falcosecurity-libs
Length of output: 50384
🏁 Script executed:
Repository: stackrox/falcosecurity-libs
Length of output: 50385
🏁 Script executed:
Repository: stackrox/falcosecurity-libs
Length of output: 41125
🏁 Script executed:
Repository: stackrox/falcosecurity-libs
Length of output: 50383
🏁 Script executed:
Repository: stackrox/falcosecurity-libs
Length of output: 50383
Make
PT_CHARBUFformatting length-aware.Malformed or capture-file input can produce
strnlen(param_data, param_len) == param_len. The fallback then returns astd::string_viewwithout a NUL, butuserspace/libsinsp/event.cpp:877passess.data()to%s. The destination bound does not limit source reads. Use a length-aware formatter or reject the no-NUL case before formatting.🤖 Prompt for AI Agents