LiveActive security incident?Get immediate response
CVE Record

CVE-2021-46879: An issue was discovered in Treasure Data Fluent Bit 1.7.1, a wrong variable is used to get the msgpack data...

An issue was discovered in Treasure Data Fluent Bit 1.7.1, a wrong variable is used to get the msgpack data resulting in a heap overflow in flb_msgpack_gelf_value_ext. An attacker can craft a malicious file and tick the victim to open the file with the software, triggering a heap overflow and execute arbitrary code on the target system.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-46879 is a heap overflow in Treasure Data Fluent Bit 1.7.1. A malicious file could trigger memory corruption when opened by a victim, potentially allowing arbitrary code execution. The attack requires local user interaction, so urgency depends on whether vulnerable Fluent Bit tooling processes untrusted files.

Executive priority

Treat this as a targeted high-severity remediation item, not an internet-wide emergency. Prioritize environments that use Fluent Bit 1.7.1 on analyst workstations, servers, or pipelines handling external files, because successful exploitation could execute code in the victim process context.

Technical view

The issue is a CWE-787 out-of-bounds write in flb_msgpack_gelf_value_ext caused by using the wrong variable to retrieve msgpack data. CVSS 3.1 is 7.8 high: local attack vector, low complexity, no privileges, user interaction required, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where Fluent Bit 1.7.1 is installed and users or automation can open or process attacker-supplied files. The source bundle does not provide complete affected CPEs or product matrices, so validation should focus on deployed Fluent Bit versions and file-handling workflows.

Exploitation context

The CVE description says exploitation requires crafting a malicious file and tricking the victim into opening it. The source bundle does not cite active exploitation, public weaponization, or CISA KEV listing; KEV is false.

Researcher notes

Evidence is limited to the CVE text, OSS-Fuzz reference, and Fluent Bit PR #3100 reference. The bundle does not include a named fixed version, affected CPEs, or exploitation reports. Avoid expanding scope beyond Fluent Bit 1.7.1 unless vendor release notes confirm broader affected versions.

Mitigation direction

  • Inventory Fluent Bit installations and identify any running version 1.7.1.
  • Review Fluent Bit PR #3100 and project guidance for the fixed release.
  • Upgrade vulnerable deployments after confirming the maintained fixed version.
  • Restrict vulnerable tooling from opening or processing untrusted local files.
  • Prioritize systems where Fluent Bit runs with elevated privileges.

Validation and detection

  • Check installed Fluent Bit versions across endpoints, servers, containers, and build images.
  • Identify workflows that import or open local msgpack, GELF, or log files.
  • Confirm whether deployed builds include the fix referenced by PR #3100.
  • Review endpoint telemetry for crashes around Fluent Bit file processing.
  • Document compensating controls where upgrades are pending.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-46879 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2021-46879Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.