-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Buffer over-read in systemd input plugin since v3.2.3 #9788
Labels
Comments
5 tasks
bpetermannS11
added a commit
to bpetermannS11/fluent-bit
that referenced
this issue
Jan 2, 2025
Fix buffer over-reads in systemd input plugin (fluent#9788). In systemd_enumerate_data_store: when copying the item value the input string may not be 0-terminated, so relying on strlen may lead to reads beyond the end of the buffer. Use the known string length instead of strlen. Signed-off-by: Bodo Petermann <[email protected]>
edsiper
pushed a commit
that referenced
this issue
Jan 8, 2025
Fix buffer over-reads in systemd input plugin (#9788). In systemd_enumerate_data_store: when copying the item value the input string may not be 0-terminated, so relying on strlen may lead to reads beyond the end of the buffer. Use the known string length instead of strlen. Signed-off-by: Bodo Petermann <[email protected]>
edsiper
pushed a commit
that referenced
this issue
Jan 8, 2025
Fix buffer over-reads in systemd input plugin (#9788). In systemd_enumerate_data_store: when copying the item value the input string may not be 0-terminated, so relying on strlen may lead to reads beyond the end of the buffer. Use the known string length instead of strlen. Signed-off-by: Bodo Petermann <[email protected]>
Fixed in #9789. |
edsiper
pushed a commit
that referenced
this issue
Jan 22, 2025
Fix buffer over-reads in systemd input plugin (#9788). In systemd_enumerate_data_store: when copying the item value the input string may not be 0-terminated, so relying on strlen may lead to reads beyond the end of the buffer. Use the known string length instead of strlen. Signed-off-by: Bodo Petermann <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Describe the bug
When running fluent-bit with the systemd input plugin some buffer over-read occur while the plugin handles the journal data, apparently while copying structured data item values.
Valgrind complains "Conditional jump or move depends on uninitialised value(s)" when running fluent-bit v3.2.3 or v3.2.4, the offending code is in
systemd_enumerate_data_store
.To Reproduce
Run fluent-bit with the following configuration and some systemd journal activity:
Expected behavior
No reads from uninitialized memory
Screenshots
Your Environment
Additional context
The text was updated successfully, but these errors were encountered: