cve.bz

CVE-2022-39379 Deserialization of Untrusted Data

9.8 criticalEPSS 45%Fix available

Critical (9.8). EPSS 45% estimated probability of exploitation activity in the next 30 days. Fixed in fluentd 1.15.3.

On this page
Fluentd collects events from various data sources and writes them to files, RDBMS, NoSQL, IaaS, SaaS, Hadoop and so on. A remote code execution (RCE) vulnerability in non-default configurations of Fluentd allows unauthenticated attackers to execute arbitrary code via specially crafted JSON payloads. Fluentd setups are only affected if the environment variable `FLUENT_OJ_OPTION_MODE` is explicitly set to `object`. Please note: The option FLUENT_OJ_OPTION_MODE was introduced in Fluentd version 1.13.2. Earlier versions of Fluentd are not affected by this vulnerability. This issue was patched in version 1.15.3. As a workaround do not use `FLUENT_OJ_OPTION_MODE=object`.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
45% (unchanged from 45% a week ago; 45% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2025-04-23. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-39379 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-39379?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-39379?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-39379 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
fluentd:fluentdfrom 1.13.2 before 1.15.3
fedoraproject:fedora37

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-fppq-mj76-fpj2RubyGemsfluentd>=1.13.2 <1.15.31.15.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Azure Linux2rubygem-fluentd1.14.6-2AZL-11396

From the distributions' data via OSV.dev: Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits.

Red Hat

Red Hat rates this Moderate.

Red Hat's statement

The Fluentd setups are only affected if the environment variable FLUENT_OJ_OPTION_MODE is explicitly set to object, which is a non-default configuration. Hence, this CVE is categorized as Moderate impact.

ProductPackageStateAdvisory
Logging Subsystem for Red Hat OpenShiftopenshift-logging/fluentd-rhel9Not affected
Red Hat OpenShift Container Platform 3.11fluentdOut of support scope
Red Hat OpenShift Container Platform 3.11openshift3/logging-fluentdOut of support scope
Red Hat OpenShift Container Platform 3.11openshift3/ose-logging-fluentdOut of support scope
Red Hat OpenStack Platform 13 (Queens)puppet-fluentdOut of support scope
Red Hat OpenStack Platform 13 (Queens)rhosp13/openstack-fluentdOut of support scope

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2022-39379.

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON