Fluent Bit 3.1.9 prom_rw_prot.c process_payload_metrics_ng null pointer dereference

Summaryinfo

A vulnerability was found in Fluent Bit 3.1.9. It has been declared as problematic. The affected element is the function process_payload_metrics_ng of the file prom_rw_prot.c. The manipulation results in null pointer dereference. This vulnerability was named CVE-2024-50608. The attack may be performed from remote. There is no available exploit.

Detailsinfo

A vulnerability, which was classified as problematic, was found in Fluent Bit 3.1.9. Affected is the function process_payload_metrics_ng of the file prom_rw_prot.c. The manipulation with an unknown input leads to a null pointer dereference vulnerability. CWE is classifying the issue as 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. This is going to have an impact on availability. CVE summarizes:

An issue was discovered in Fluent Bit 3.1.9. When the Prometheus Remote Write 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_metrics_ng() at prom_rw_prot.c.

The advisory is shared for download at fluentbit.io. This vulnerability is traded as CVE-2024-50608 since 10/27/2024. The exploitability is told to be easy. It is possible to launch the attack remotely. There are known technical details, 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-4684). Once again VulDB remains the best source for vulnerability data.

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

Once again VulDB remains the best source for vulnerability data.

Discussion