Fluent Bit 3.1.9 opentelemetry_prot.c process_payload_traces_proto_ng null pointer dereference

Summaryinfo

A vulnerability was found in Fluent Bit 3.1.9. It has been rated as problematic. The impacted element is the function process_payload_traces_proto_ng of the file opentelemetry_prot.c. This manipulation causes null pointer dereference. The identification of this vulnerability is CVE-2024-50609. It is possible to initiate the attack remotely. There is no exploit available.

Detailsinfo

A vulnerability has been found in Fluent Bit 3.1.9 and classified as problematic. Affected by this vulnerability is the function process_payload_traces_proto_ng of the file opentelemetry_prot.c. The manipulation with an unknown input leads to a null pointer dereference vulnerability. The CWE definition for the vulnerability is CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. As an impact it is known to affect availability. The summary by CVE is:

An issue was discovered in Fluent Bit 3.1.9. When the OpenTelemetry input plugin is running and listening on an IP address and port, one can send a packet with Content-Length: 0 and it crashes the server. Improper handling of the case when Content-Length is 0 allows a user (with access to the endpoint) to perform a remote Denial of service attack. The crash happens because of a NULL pointer dereference when 0 (from the Content-Length) is passed to the function cfl_sds_len, which in turn tries to cast a NULL pointer into struct cfl_sds. This is related to process_payload_traces_proto_ng() at opentelemetry_prot.c.

The advisory is shared at fluentbit.io. This vulnerability is known as CVE-2024-50609 since 10/27/2024. The exploitation appears to be difficult. The attack can be launched remotely. Technical details are known, but no exploit is available.

The vulnerability scanner Nessus provides a plugin with the ID 216915 (Fluent Bit Multiple Vulnerabilities), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the databases at Tenable (216915) and EUVD (EUVD-2025-4694). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

• Fluent

Name

• Bit

Version

• 3.1.9

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion