Process crash via unchecked allocation failure
Published Feb 10, 2021 · Updated Aug 3, 2024
NULL pointer dereference in Treasure Data Fluent Bit 1.6.10 allows remote attackers to crash the process through allocation failure. The Avro conversion function and HTTP metrics handlers use flb_malloc results without checking for NULL before passing or dereferencing them. The network path requires the optional built-in HTTP server, while the Avro path requires an allocation failure during record conversion.
Summary
What happened
NULL pointer dereference in Treasure Data Fluent Bit 1.6.10 allows remote attackers to crash the process through allocation failure. The Avro conversion function and HTTP metrics handlers use flb_malloc results without checking for NULL before passing or dereferencing them. The network path requires the optional built-in HTTP server, while the Avro path requires an allocation failure during record conversion.
The record
- CVE
- CVE-2021-27186
- Published
- Feb 10, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-476, T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 10, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo