A vulnerability in Fluent Bit versions 2.1.8 through 2.2.1 allows a remote attacker to trigger a NULL pointer dereference by sending an invalid HTTP payload with the content type x-www-form-urlencoded. This causes the Fluent Bit process to crash and fail to restart, resulting in a denial of service and disruption of log delivery.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept (PoC) exploit for CVE-2024-23722, a denial-of-service (DoS) vulnerability in Fluent Bit versions 2.1.8 through 2.2.1. The exploit consists of a single Python script ('exploit.py') and a README file. The script repeatedly sends HTTP POST requests with a minimal payload to a specified target URL, aiming to crash the server by exploiting the vulnerability. The README provides usage instructions and references a write-up for further details. The exploit targets network-accessible HTTP endpoints and is intended for use against vulnerable Fluent Bit instances. No advanced payload or post-exploitation functionality is present; the exploit is a simple DoS PoC.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.