-
Notifications
You must be signed in to change notification settings - Fork 2k
in_kubernetes_events: fix OOB reads from non-NUL-terminated msgpack strings #12187
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
Closed
zanarellidev
wants to merge
3
commits into
fluent:master
from
zanarellidev:fix/k8s-events-msgpack-string-oob-read
Closed
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
4a92298
in_kubernetes_events: fix OOB reads from non-NUL-terminated msgpack s…
zanarellidev 3897b6e
in_kubernetes_events: tighten timestamp and uint64 parsing validation
zanarellidev 10e922c
in_kubernetes_events: reject signed uint64 strings in record_get_fiel…
zanarellidev 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
Oops, something went wrong.
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.
When
FLB_HAVE_SQLDBis enabled and thedboption is configured, this exact-length lookup makesk8s_events_sql_insert_event()stop finding the event metadata map: that function still callsrecord_get_field_ptr(item, "meta"), which previously matched the Kubernetes"metadata"key only because the old code accepted prefixes. With this change the insert path always logsunable to find metadata to save event, so the database never records processed UIDs and DB-backed duplicate filtering no longer works; update that caller to request"metadata"before relying on exact key matching.Useful? React with 👍 / 👎.