KNOWLEDGE BASE
NOTE: This is a minor hotfix release that covers for corner cases for metrics handling. We keep same
release notes as part of v2
Release Notes v2.2.3
Fluent Bit is a Fast and Lightweight Data Processor and Forwarder for Linux,
BSD and OSX. We are proud to announce the availability of Fluent Bit v2.2.3.
Introduction
Fluent Bit v2.2 is currently is maintenance only with security fixes. This specific version is a one-off due to a security issue found in the HTTP endpoint (CVE-2024-4323). It also contains other fixes that were not released before v3.0 series:
-
Core
- http_server: api: v1: backport fix for CVE-2024-4323
- engine_dispatch: remove chunks from memory if the task fails to be created
- log_cache: avoid double free by setting the log_cache pointer to NULL.
- task: expose map_get_task_id to add a check in engine_dispatch
- sched: use sched->evl when freeing the scheduler timer.
- sched: free the base timer used by the scheduler.
- network: Fix int-conversion error by using POSIX version of strerror_r
- utils: Remove a needless flb_free
- output_thread: destroy thread events channel on shutdown.
- engine: destroy self events channels on shutdown.
- reload: Mark hot reloading for the old context
- api: v2: reload: Distinguish the status of hot reloading
- input_chunk: added proper accounting of chunks that are rolled over
- config: release data pipe using flb_pipe_destroy.
- log: use flb_pipe_destroy to close worker log pipe on error.
- log: free log worker pipe when appropriate.
- Plugins
- Calyptia_Fleet (Input)
- Fix memory leak when setting conf_path_file.
- Code style cleanup
- Improve connection context handling
- Remove double free of cfl_array_destroy()
- Kubernetes_Events (Input)
- Refactor time check to use struct flb_time. (#8845)
- HTTP (Input)
- Adds support for content-encoding: gzip (#7667)
- Forward (Output)
- Fix memory leak during connection loss
Contributors
On every release, there are many people involved doing contributions on different areas like bug reporting, troubleshooting, documentation and coding, without these contributions from the community, the project won’t be the same and won’t be in the good shape that it is now. So THANK YOU! to everyone who takes part of this journey!
Join us
We want to hear about you, our community is growing and you can be part of it!, you can contact us at: