BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2021
CVE-2021-45046High confidence

Apache Log4j2 Deserialization of Untrusted Data Vulnerability

Apache · Log4j2

9.0CriticalCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

CISA confirms exploitation in the wild and lists 2023-05-22 as the remediation due date. Verified remediation exists for at least one product or source, but 7 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityCriticalOperational priority:Critical, unchanged from published severity.unchanged

Evidence used

  • CISA confirms exploitation in the wild.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 99.98% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Increase monitoring for the attack path and post-exploitation behaviour described in the report.

Verification

  1. Confirm that the asset runs Apache Log4j2 and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 3 daysRemediation target: Within 90 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 7 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

Debian findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

4 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourceapache-log4j2Vendor fix publishedDebian records a fixed source-package version for this release.2.16.0-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian bookwormbookworm · sourceapache-log4j2Vendor fix publishedDebian records a fixed source-package version for this release.2.16.0-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian forkyforky · sourceapache-log4j2Vendor fix publishedDebian records a fixed source-package version for this release.2.16.0-1Debian Security Tracker ↗Source updated 6 Oct 2026
Debian sidsid · sourceapache-log4j2Vendor fix publishedDebian records a fixed source-package version for this release.2.16.0-1Debian Security Tracker ↗Source updated 6 Oct 2026
Open-source package ranges14 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenorg.apache.logging.log4j:log4j-coreECOSYSTEM: introduced 2.13.0; fixed 2.16.02.16.0OSV record ↗aggregator derived · 2 Oct 2026
Mavenorg.apache.logging.log4j:log4j-coreECOSYSTEM: introduced 2.4.0; fixed 2.12.22.12.2OSV record ↗aggregator derived · 2 Oct 2026
Mavenorg.apache.logging.log4j:log4j-coreECOSYSTEM: introduced 0; fixed 2.3.12.3.1OSV record ↗aggregator derived · 2 Oct 2026
Mavenorg.ops4j.pax.logging:pax-logging-log4j2ECOSYSTEM: introduced 1.8.0; fixed 1.9.21.9.2OSV record ↗aggregator derived · 2 Oct 2026
Mavenorg.ops4j.pax.logging:pax-logging-log4j2ECOSYSTEM: introduced 1.10.0; fixed 1.10.81.10.8OSV record ↗aggregator derived · 2 Oct 2026
Mavenorg.ops4j.pax.logging:pax-logging-log4j2ECOSYSTEM: introduced 1.11.0; fixed 1.11.111.11.11OSV record ↗aggregator derived · 2 Oct 2026
Mavenorg.ops4j.pax.logging:pax-logging-log4j2ECOSYSTEM: introduced 2.0.0; fixed 2.0.122.0.12OSV record ↗aggregator derived · 2 Oct 2026
mavenorg.apache.logging.log4j:log4j-core>= 2.13.0, < 2.16.02.16.0GitHub advisory ↗github reviewed aggregator · 2 Oct 2026
mavenorg.apache.logging.log4j:log4j-core>= 2.4.0, < 2.12.22.12.2GitHub advisory ↗github reviewed aggregator · 2 Oct 2026
mavenorg.apache.logging.log4j:log4j-core< 2.3.12.3.1GitHub advisory ↗github reviewed aggregator · 2 Oct 2026
mavenorg.ops4j.pax.logging:pax-logging-log4j2>= 1.8.0, < 1.9.21.9.2GitHub advisory ↗github reviewed aggregator · 2 Oct 2026
mavenorg.ops4j.pax.logging:pax-logging-log4j2>= 1.10.0, < 1.10.81.10.8GitHub advisory ↗github reviewed aggregator · 2 Oct 2026
mavenorg.ops4j.pax.logging:pax-logging-log4j2>= 1.11.0, < 1.11.111.11.11GitHub advisory ↗github reviewed aggregator · 2 Oct 2026
mavenorg.ops4j.pax.logging:pax-logging-log4j2>= 2.0.0, < 2.0.122.0.12GitHub advisory ↗github reviewed aggregator · 2 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

5 current
CVE-2021-45046 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitylog4j-core: DoS in log4j 2.x with thread context message pattern and context lookup pattern (incomplete fix for CVE-2021-44228)
4 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • log4j-core as a component of Red Hat Integration Camel Quarkus 1
  • opendaylight as a component of Red Hat OpenStack Platform 13 (Queens)
  • opendaylight.src as a component of Red Hat OpenStack Platform 13 (Queens)
  • log4j-core as a component of streams for Apache Kafka
Summary
A flaw was found in the Apache Log4j logging library in versions from 2.0.0 and before 2.16.0. A remote attacker with control over Thread Context Map (MDC) input data could craft malicious input using a JNDI Lookup pattern resulting in remote code execution (RCE) in a limited number of environments.
Remediation
Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
SESB-2021-347-01 · CSAF 2.0 · revision 14.0.0 · finalSchneider Electric CPCERTApache Log4j Vulnerabilities (Log4Shell)
12 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • Schneider Electric APC PowerChute Business Edition version 9.5
  • Schneider Electric APC PowerChute Business Edition version 10.0
  • Schneider Electric APC PowerChute Business Edition version 10.0.1
  • Schneider Electric APC PowerChute Business Edition version 10.0.2
  • Schneider Electric APC PowerChute Business Edition version 10.0.3
  • Schneider Electric APC PowerChute Business Edition version 10.0.4
  • Schneider Electric APC PowerChute Network Shutdown (PCNS) version 4.4.1
  • Schneider Electric APC PowerChute Network Shutdown (PCNS) version 4.4
  • Schneider Electric APC PowerChute Network Shutdown (PCNS) version 4.3
  • Schneider Electric APC PowerChute Network Shutdown (PCNS) version 4.2
  • Schneider Electric EcoStruxure™ IT Gateway =1.13.1.5
  • Schneider Electric Harmony Configurator version 33 and prior
Summary
Log4j is an open-source Java logging library developed by the Apache Foundation which is widely used by both enterprise applications and cloud services. The recent Apache Log4j vulnerabilities are listed below and have ratings ranging from High to Critical. CVE-2021-44228 (Log4Shell), received a rating of Critical and can allow an attacker who can control log messages or log message parameters to execute arbitrary code loaded from LDAP servers and other JNDI related endpoints when message lookup substitution is enabled. Exploitation could allow for unauthenticated remote code execution (RCE) and possibly access to servers. Additional CVEs within the scope of this security notification: CVE-2021-44228 CVE-2021-45046 CVE-2021-45105 CVE-2021-4104 CVE-2021-44832 For more information, please visit the Apache logging services log4j security page https://logging.apache.org/log4j/2.x/security.html.
Remediation
Schneider Electric has deployed a fix to update SDK-UMS to Log4j 2.17. These fixes have been deployed automatically and require no action from customers.
SSA-714170 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-714170: Apache Log4j Vulnerabilities (Log4Shell, CVE-2021-44228, CVE-2021-45046) - Impact to SPPA-T3000
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • SPPA-T3000 SeS3000 Security Server (6DU7054-0..00-..A0)
Summary
The fix to address CVE-2021-44228 was incomplete in certain non-default configurations, when the logging configuration uses a non-default Pattern Layout with a Context Lookup (for example, ${ctx:loginId}). This could allow attackers with control over Thread Context Map (MDC) input data to craft malicious input data using a JNDI Lookup pattern, resulting in an information leak and remote code execution in some environments and local code execution in all environments.
Remediation
Specific mitigations and how to apply are described in the SE Controls Security Announcement Incident 2021-01, available in the customer portal. https://cep.siemens-energy.com/cep/
SSA-479842 · CSAF 2.0 · revision 2 · interimSiemens ProductCERTSSA-479842: Apache Log4j Vulnerabilities - Impact to Siemens Energy Sensformer / Sensgear (Platform, Basic and Advanced)
5 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • Sensformer / Sensgear Platform (6BK1602-0AA12-0TP0)
  • Sensformer / Sensgear Platform (6BK1602-0AA22-0TP0)
  • Sensformer / Sensgear Platform (6BK1602-0AA32-0TP0)
  • Sensformer / Sensgear Platform (6BK1602-0AA42-0TP0)
  • Sensformer / Sensgear Platform (6BK1602-0AA52-0TP0)
Summary
The fix to address CVE-2021-44228 was incomplete in certain non-default configurations, when the logging configuration uses a non-default Pattern Layout with a Context Lookup (for example, ${ctx:loginId}). This could allow attackers with control over Thread Context Map (MDC) input data to craft malicious input data using a JNDI Lookup pattern, resulting in an information leak and remote code execution in some environments and local code execution in all environments.
Remediation
Vulnerabilities fixed on central cloud service between 2021-12-10 (CVE-2021-44228) and 2021-12-21 (CVE-2021-45105); no user actions necessary
SSA-397453 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-397453: Apache Log4j Vulnerabilities (Log4Shell, CVE-2021-44228, CVE-2021-45046) - Impact to Siemens Energy TraceAlertServerPLUS
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • TraceAlertServerPLUS
Summary
The fix to address CVE-2021-44228 was incomplete in certain non-default configurations, when the logging configuration uses a non-default Pattern Layout with a Context Lookup (for example, ${ctx:loginId}). This could allow attackers with control over Thread Context Map (MDC) input data to craft malicious input data using a JNDI Lookup pattern, resulting in an information leak and remote code execution in some environments and local code execution in all environments.
Remediation
Open TraceAlertServerPLUS.exe with Zip tool to remove file JndiLookup.class in directory org/apache/logging/log4j/core/lookup/. This measure mitigates both CVE-2021-44228 and CVE-2021-45046.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2021-34769

CISA KEV mirrored by ENISA

It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.

EUVD state
Present in the current official mapping
Known exploitation
Recorded by ENISA since 1 May 2023. Evidence sources: cisa_kev.
ENISA score
9.0 · CVSS 3.1
Advisory evidence
33 linked advisory records
Explicit mitigation evidence

Only statements that explicitly mention a fix, patch, update, workaround or mitigation are shown here.

  • csaf_redhat · RHSA-2021:5127Red Hat Security Advisory: Openshift Logging security and bug update (5.2.4)
  • csaf_redhat · RHSA-2021:5106Red Hat Security Advisory: OpenShift Container Platform 4.6.z security update
  • csaf_redhat · RHSA-2022:0083Red Hat Security Advisory: Red Hat build of Eclipse Vert.x 4.1.8 security update
  • csaf_redhat · RHSA-2021:5094Red Hat Security Advisory: OpenShift Container Platform 3.11.z security update
  • csaf_redhat · RHSA-2021:5128Red Hat Security Advisory: Openshift Logging security and bug update (5.1.5)
  • csaf_redhat · RHSA-2022:0223Red Hat Security Advisory: Red Hat Integration Camel-K 1.6.3 release and security update
  • csaf_redhat · RHSA-2021:5108Red Hat Security Advisory: OpenShift Container Platform 4.8.z security update
  • csaf_redhat · RHSA-2021:5148Red Hat Security Advisory: OpenShift Container Platform 4.8.24 extras security update
  • csaf_redhat · RHSA-2021:5107Red Hat Security Advisory: OpenShift Container Platform 4.7.40 security update
  • csaf_redhat · RHSA-2021:5141Red Hat Security Advisory: OpenShift Container Platform 4.6.52 security update
  • csaf_redhat · RHSA-2025:1746Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.1.9 on RHEL 7 security update
  • csaf_redhat · RHSA-2022:1299Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.4 security update
  • csaf_redhat · RHSA-2022:0216Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4 security update
  • csaf_redhat · RHSA-2022:0205Red Hat Security Advisory: Red Hat Data Grid 8.2.3 security update
  • csaf_redhat · RHSA-2021:5129Red Hat Security Advisory: Openshift Logging security and bug update (5.3.1)
  • csaf_opensuse · openSUSE-SU-2021:4107-1Security update for log4j
  • csaf_redhat · RHSA-2022:0203Red Hat Security Advisory: Red Hat Fuse 7.8-7.10 security update
  • csaf_redhat · RHSA-2022:0138Red Hat Security Advisory: Red Hat AMQ Streams 2.0.0 release and security update
  • csaf_redhat · RHSA-2022:1296Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.4 security update
  • csaf_redhat · RHSA-2022:1297Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.4 security update
  • csaf_redhat · RHSA-2025:1747Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.3.12 security update
  • csaf_opensuse · openSUSE-SU-2021:4094-1Security update for log4j
  • csaf_redhat · RHSA-2021:5140Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4 security update
  • csaf_opensuse · openSUSE-SU-2021:1601-1Security update for log4j
  • csaf_redhat · RHSA-2022:0222Red Hat Security Advisory: Red Hat Integration Camel Extensions for Quarkus 2.2 security update
Recommended actionPatch only the product branches with a verified fix

CISA confirms exploitation in the wild and lists 2023-05-22 as the remediation due date. Verified remediation exists for at least one product or source, but 7 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

Apache Log4j2 contains a deserialization of untrusted data vulnerability due to the incomplete fix of CVE-2021-44228, where the Thread Context Lookup Pattern is vulnerable to remote code execution in certain non-default configurations.

What

Apache Log4j2 contains a deserialization of untrusted data vulnerability due to the incomplete fix of CVE-2021-44228, where the Thread Context Lookup Pattern is vulnerable to remote code execution in certain non-default configurations.

Why

The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

What

Apache Log4j2 contains a deserialization of untrusted data vulnerability due to the incomplete fix of CVE-2021-44228, where the Thread Context Lookup Pattern is vulnerable to remote code execution in certain non-default configurations.

Why

The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
Confirmed in the wild

CISA added this CVE to its Known Exploited Vulnerabilities catalogue on 2023-05-01. Known ransomware campaign use is recorded.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') → execute code or commands in the affected security context
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Changed: exploitation can affect a different security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-917 ↗

CWE-917: Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection'). The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkUnauthenticatedRemote code executionCWE-917CISA KEV
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

ENISA EUVD · EUVD-2021-34769Known-exploited evidence recorded

It was found that the fix to address CVE-2021-44228 in Apache Log4j 2.15.0 was incomplete in certain non-default configurations. This could allows attackers with control over Thread Context Map (MDC) input data when the logging configuration uses a non-default Pattern Layout with either a Context Lookup (for example, $${ctx:loginId}) or a Thread Context Map pattern (%X, %mdc, or %MDC) to craft malicious input data using a JNDI Lookup pattern resulting in an information leak and remote code execution in some environments and local code execution in all environments. Log4j 2.16.0 (Java 8) and 2.12.2 (Java 7) fix this issue by removing support for message lookup patterns and disabling JNDI functionality by default.

Official EUVD record ↗
BSI · German · WID-SEC-2026-1203Oracle Fusion Middleware: Mehrere Schwachstellen

Ein entfernter, anonymer oder authentisierter Angreifer kann mehrere Schwachstellen in Oracle Fusion Middleware ausnutzen, um die Vertraulichkeit, Integrität und Verfügbarkeit zu gefährden.

Official advisory ↗
BSI · German · WID-SEC-2023-0063Juniper Junos Space: Mehrere Schwachstellen

Ein Angreifer aus dem angrenzenden Netzwerk oder ein entfernter anonymer, authentisierter oder lokaler Angreifer kann mehrere Schwachstellen in Juniper Junos Space ausnutzen, um Sicherheitsmaßnahmen zu umgehen, vertrauliche Informationen offenzulegen, einen Denial-of-Service-Zustand auszulösen, beliebigen Code auszuführen und seine Privilegien zu erweitern.

Official advisory ↗
BSI · German · WID-SEC-2022-0352Apache log4j: Schwachstelle ermöglicht Codeausführung

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Apache log4j ausnutzen, um beliebigen Code auszuführen.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV21-652Palo Alto Networks security advisory

On 10 December 2021 Palo Alto Networks published a Security Advisory to address critical vulnerabilities which may affect multiple products using the Apache Log4j logging utility. Exploitation of these vulnerabilities could lead to remote code execution.

Official advisory ↗
Canadian Centre for Cyber Security · English · AV21-657Citrix security advisory

On 11 December 2021 Citrix published a Security Advisory to address critical vulnerabilities which may affect multiple products using the Apache Log4j logging utility. Exploitation of these vulnerabilities could lead to remote code execution.

Official advisory ↗
Canadian Centre for Cyber Security · English · AL21-019Active exploitation of Apache Log4j vulnerability - update 7

On 10 December 2021, Apache released a Security Advisory Footnote 1 Footnote 2 highlighting a critical remote code execution vulnerability in Log4j, a widely deployed Java-based logging utility. Open-source reporting indicates that active scanning and exploitation of this vulnerability have been observed.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20211215Security Bulletin 15 Dec 2021

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 15 Dec 2021, published on 15 December 2021. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0855Multiples vulnérabilités dans les produits Juniper Networks

ecord?id=CVE-2021-22146 Référence CVE CVE-2021-3903 https://www.cve.org/CVERecord?id=CVE-2021-3903 Référence CVE CVE-2021-40153 https://www.cve.org/CVERecord?id=CVE-2021-40153 Référence CVE CVE-2021-4104 https://www.cve.org/CVERecord?id=CVE-2021-4104 Référence CVE CVE-2021-41043 https://www.cve.org/CVERecord?id=CVE-2021-41043 Référence CVE CVE-2021-41072 https://www.cve.org/CVERecord?id=CVE-2021-41072 Référence CVE CVE-2021-42550 https://www.cve.org/CVERecord?id=CVE-2021-42550 Référence CVE CVE-2021-44228 https://www.cve.org/CVERecord?id=CVE-2021-44228 Référence CVE CVE-2021-44832 https://www.cve.org/CVERecord?id=CVE-2021-44832 Référence CVE CVE-2021-45046 https://www.cve.org/CVERecord?id=CVE-2021-45046 Référence CVE CVE-2021-45105 https://www.cve.org/CVERecord?id=CVE-2021-45105 Référence CVE CVE-2021-47606 https://www.cve.org/CVERecord?id=CVE-2021-47606 Référence CVE CVE-2022-24805 https://www.cve.org/CVERecord?id=CVE-2022-24805 Référence CVE CVE-2022-24806 https://www.cve.org/CVERecord?id=CVE-2022-24806 Référence CVE CVE-2022-24807 https://www.cve.org/CVERecord?id=CVE-2022-24807 Référence CVE CVE-2022-24808 https://www.cve.org/CVERecord?id=CVE-2022-24808 Référence CVE CVE-2022-24810 https://www.cve.org/CVERecord?id=CVE-2022-24810 Référence CVE CVE-2022-48622 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-717Multiples vulnérabilités dans les produits Schneider

ord?id=CVE-2021-22782 Référence CVE CVE-2021-22786 https://www.cve.org/CVERecord?id=CVE-2021-22786 Référence CVE CVE-2021-22789 https://www.cve.org/CVERecord?id=CVE-2021-22789 Référence CVE CVE-2021-22790 https://www.cve.org/CVERecord?id=CVE-2021-22790 Référence CVE CVE-2021-22791 https://www.cve.org/CVERecord?id=CVE-2021-22791 Référence CVE CVE-2021-22792 https://www.cve.org/CVERecord?id=CVE-2021-22792 Référence CVE CVE-2021-4104 https://www.cve.org/CVERecord?id=CVE-2021-4104 Référence CVE CVE-2021-44228 https://www.cve.org/CVERecord?id=CVE-2021-44228 Référence CVE CVE-2021-44832 https://www.cve.org/CVERecord?id=CVE-2021-44832 Référence CVE CVE-2021-45046 https://www.cve.org/CVERecord?id=CVE-2021-45046 Référence CVE CVE-2021-45105 https://www.cve.org/CVERecord?id=CVE-2021-45105 Référence CVE CVE-2022-34759 https://www.cve.org/CVERecord?id=CVE-2022-34759 Référence CVE CVE-2022-34760 https://www.cve.org/CVERecord?id=CVE-2022-34760 Référence CVE CVE-2022-34761 https://www.cve.org/CVERecord?id=CVE-2022-34761 Référence CVE CVE-2022-34762 https://www.cve.org/CVERecord?id=CVE-2022-34762 Référence CVE CVE-2022-34763 https://www.cve.org/CVERecord?id=CVE-2022-34763 Référence CVE CVE-2022-34764 https://www.cve.org/CVERecord?id=CVE-2022-34764 Référence CVE CVE-2022-34765 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-570Multiples vulnérabilités dans les produits IBM

VERecord?id=CVE-2018-1320 Référence CVE CVE-2019-0205 https://www.cve.org/CVERecord?id=CVE-2019-0205 Référence CVE CVE-2019-0210 https://www.cve.org/CVERecord?id=CVE-2019-0210 Référence CVE CVE-2020-13949 https://www.cve.org/CVERecord?id=CVE-2020-13949 Référence CVE CVE-2021-22945 https://www.cve.org/CVERecord?id=CVE-2021-22945 Référence CVE CVE-2021-22946 https://www.cve.org/CVERecord?id=CVE-2021-22946 Référence CVE CVE-2021-22947 https://www.cve.org/CVERecord?id=CVE-2021-22947 Référence CVE CVE-2021-3712 https://www.cve.org/CVERecord?id=CVE-2021-3712 Référence CVE CVE-2021-44228 https://www.cve.org/CVERecord?id=CVE-2021-44228 Référence CVE CVE-2021-45046 https://www.cve.org/CVERecord?id=CVE-2021-45046 Référence CVE CVE-2021-45105 https://www.cve.org/CVERecord?id=CVE-2021-45105 Référence CVE CVE-2022-0778 https://www.cve.org/CVERecord?id=CVE-2022-0778 Référence CVE CVE-2022-1292 https://www.cve.org/CVERecord?id=CVE-2022-1292 Référence CVE CVE-2022-1343 https://www.cve.org/CVERecord?id=CVE-2022-1343 Référence CVE CVE-2022-1434 https://www.cve.org/CVERecord?id=CVE-2022-1434 Référence CVE CVE-2022-1473 https://www.cve.org/CVERecord?id=CVE-2022-1473 Référence CVE CVE-2022-22576 https://www.cve.org/CVERecord?id=CVE-2022-22576 Référence CVE CVE-2022-27774 https://www.cve.org/CVERecord?id=CVE-2022-2

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-568Multiples vulnérabilités dans les produits IBM

Record?id=CVE-2020-9546 Référence CVE CVE-2020-9547 https://www.cve.org/CVERecord?id=CVE-2020-9547 Référence CVE CVE-2020-9548 https://www.cve.org/CVERecord?id=CVE-2020-9548 Référence CVE CVE-2021-20190 https://www.cve.org/CVERecord?id=CVE-2021-20190 Référence CVE CVE-2021-27568 https://www.cve.org/CVERecord?id=CVE-2021-27568 Référence CVE CVE-2021-29425 https://www.cve.org/CVERecord?id=CVE-2021-29425 Référence CVE CVE-2021-33813 https://www.cve.org/CVERecord?id=CVE-2021-33813 Référence CVE CVE-2021-38153 https://www.cve.org/CVERecord?id=CVE-2021-38153 Référence CVE CVE-2021-44228 https://www.cve.org/CVERecord?id=CVE-2021-44228 Référence CVE CVE-2021-45046 https://www.cve.org/CVERecord?id=CVE-2021-45046 Référence CVE CVE-2021-45105 https://www.cve.org/CVERecord?id=CVE-2021-45105 Référence CVE CVE-2022-22965 https://www.cve.org/CVERecord?id=CVE-2022-22965 Gestion détaillée du document le 17 juin 2022 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-526Multiples vulnérabilités dans les produits IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une exécution de code arbitraire et un déni de service à distance.

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-125Multiples vulnérabilités dans les produits SAP

De multiples vulnérabilités ont été découvertes dans les produits SAP. Elles permettent à un attaquant de provoquer un déni de service à distance, une atteinte à l'intégrité des données et une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-124Multiples vulnérabilités dans les produits Siemens

d?id=CVE-2021-40363 Référence CVE CVE-2021-40364 https://www.cve.org/CVERecord?id=CVE-2021-40364 Référence CVE CVE-2021-41990 https://www.cve.org/CVERecord?id=CVE-2021-41990 Référence CVE CVE-2021-41991 https://www.cve.org/CVERecord?id=CVE-2021-41991 Référence CVE CVE-2021-43336 https://www.cve.org/CVERecord?id=CVE-2021-43336 Référence CVE CVE-2021-44000 https://www.cve.org/CVERecord?id=CVE-2021-44000 Référence CVE CVE-2021-44016 https://www.cve.org/CVERecord?id=CVE-2021-44016 Référence CVE CVE-2021-44018 https://www.cve.org/CVERecord?id=CVE-2021-44018 Référence CVE CVE-2021-44228 https://www.cve.org/CVERecord?id=CVE-2021-44228 Référence CVE CVE-2021-45046 https://www.cve.org/CVERecord?id=CVE-2021-45046 Référence CVE CVE-2021-45106 https://www.cve.org/CVERecord?id=CVE-2021-45106 Référence CVE CVE-2021-46151 https://www.cve.org/CVERecord?id=CVE-2021-46151 Référence CVE CVE-2021-46152 https://www.cve.org/CVERecord?id=CVE-2021-46152 Référence CVE CVE-2021-46153 https://www.cve.org/CVERecord?id=CVE-2021-46153 Référence CVE CVE-2021-46154 https://www.cve.org/CVERecord?id=CVE-2021-46154 Référence CVE CVE-2021-46155 https://www.cve.org/CVERecord?id=CVE-2021-46155 Référence CVE CVE-2021-46156 https://www.cve.org/CVERecord?id=CVE-2021-46156 Référence CVE CVE-2021-46157 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-1027Multiples vulnérabilités dans IBM Db2

De multiples vulnérabilités ont été découvertes dans IBM Db2. Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un déni de service à distance et une atteinte à la confidentialité des données.

Official advisory ↗
CERT-FR · French · CERTFR-2021-AVI-951Multiples vulnérabilités dans le noyau Linux de RedHat

/CVERecord?id=CVE-2021-3536 Référence CVE CVE-2021-3597 https://www.cve.org/CVERecord?id=CVE-2021-3597 Référence CVE CVE-2021-3629 https://www.cve.org/CVERecord?id=CVE-2021-3629 Référence CVE CVE-2021-3690 https://www.cve.org/CVERecord?id=CVE-2021-3690 Référence CVE CVE-2021-37136 https://www.cve.org/CVERecord?id=CVE-2021-37136 Référence CVE CVE-2021-37137 https://www.cve.org/CVERecord?id=CVE-2021-37137 Référence CVE CVE-2021-37714 https://www.cve.org/CVERecord?id=CVE-2021-37714 Référence CVE CVE-2021-4104 https://www.cve.org/CVERecord?id=CVE-2021-4104 Référence CVE CVE-2021-44228 https://www.cve.org/CVERecord?id=CVE-2021-44228 Référence CVE CVE-2021-45046 https://www.cve.org/CVERecord?id=CVE-2021-45046 Référence CVE CVE-2021-45606 https://www.cve.org/CVERecord?id=CVE-2021-45606 Gestion détaillée du document le 15 décembre 2021 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.gouv.fr france.fr info.gouv.fr/risques Premier Ministre / Secrétariat Général de la Défense et de la Sécurité Nationale / Agence nationale de la sécurité des systèmes d'information

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-005429Apache Log4j における任意のコードが実行可能な脆弱性

Log4j には JNDI Lookup 機能による外部入力値の検証不備に起因して任意の Java コードを実行可能な脆弱性が存在します。 The Apache Software Foundation が提供する Log4j は、Java ベースのロギングライブラリです。Log4j には、ログに記載された文字列から一部の値を変数として評価する Lookup 機能が実装されています。 その Lookup 機能の内、JNDI Lookup 機能を悪用することにより、ログに含まれる外部の URL もしくは内部パスから Java のクラス情報をデシリアライズして実行してしまう問題（CWE-20, CVE-2021-44228）が発見されました。 これにより、遠隔の攻撃者が細工した文字列を脆弱なシステムのログに記載させ、結果として任意の Java コードをシステムに実行させることが可能です。

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-020223レッドハットの Red Hat OpenShift における信頼できないデータのデシリアライゼーションに関する脆弱性

レッドハットの Red Hat OpenShift には、信頼できないデータのデシリアライゼーションに関する脆弱性が存在します。

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-5914현재 악용되고 있는 Exploit(Update. 2023-05-01)

Apache Log4j2 contains a deserialization of untrusted data vulnerability due to the incomplete fix of CVE-2021-44228, where the Thread Context Lookup Pattern is vulnerable to remote code execution in certain non-default configurations.

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-5466Apache Log4j 보안 업데이트 권고 (Update. 22-1-3 14:40)

#### Apache Log4j 보안 업데이트 권고 (Update. 22-1-3 14:40) 2021.12.11 2021-12-12 : 영향 받는 버전 및 참고 사이트 추가 2021-12-13 : 1.x 버전 사용자 최신 업데이트 권고 및 버전확인방법 추가 2021-12-13 : 탐지정책 추가 2021-12-15 : CVE-2021-45046, CVE-2021-4104 추가, 대응방안 수정 2021-12-16 : 대응방안 수정 2021-12-17 : 취약점 주요내용 수정 2021-12-22 : 영향받는 버전 및 대응방안 수정 2022-1-3 : 영향받는 버전 수정 ##### □ 개요 o Apache 소프트웨어 재단은 자사의 Log4j 2에서 발생하는 취약점을 해결한 보안 업데이트 권고[1] o 공격자는 해당 취약점을 이용하여 악성코드 감염 등의 피해를 발생시킬수 있으므로, 최신 버전으로 업데이트 권고 ※ 관련 사항은 참고사이트 [6] 취약점 대응가이드를 참고 바랍니다. ※ 참고 사이트 [4]를 확인하여 해당 제품을 이용 중일 경우, 해당 제조사의 권고에 따라 패치 또는 대응 방안 적용 ※ Log4j 취약점을 이용한 침해사고 발생시 한국인터넷진흥원에 신고해 주시기 바랍니다. ##### □ 주요 내용 o Apache Log4j 2에서 발생하는 원격코드 실행 취약점(CVE-2021-44228)[2] o Apache Log4j 2에서 발생하는 원격코드 실행 취약점(CVE-2021-45046)[7] o Apache Log4j 1.x에서 발생하는 원격코드 실행 취약점(CVE-2021-4104)[8] ※ Log4j : 프로그램 작성 중 로그를 남기기 위해 사용되는 자바 기반의 오픈소스 유틸리티

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
Fixed
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
A mitigation or workaround reference is available from the source linked below; validate it against the affected product and version.
04

Evidence and provenance

Published 14 Dec 2021 · Last source change 21 Oct 2025, 23:25 UTC · CWE-917 · Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')

CVE recordCVE.org · 5.1
CVSS sourceNIST NVD
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2021-34769
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    Apache Log4j: Apache Log4j2 < 2.16.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    Apache Log4j: Apache Log4j2 < 2.16.0 · Fixed: Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Vendor guidanceAuthoritative vendor guidance changed: added remediation: oracle.com/cpujan2022.html; removed remediation: access.redhat.com/CVE-2021-45046.
    Before
    mitigation: logging.apache.org/security.html · mitigation: openwall.com/4 · patch: oracle.com/cpujan2022.html · 1 more references
    After
    mitigation: logging.apache.org/security.html · mitigation: openwall.com/4 · patch: oracle.com/cpujan2022.html · 1 more references
    oracle.com ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    Apache Log4j: Apache Log4j2 < 2.16.0 · Fixed: Before applying this update, ensure all previously released errata relevant to your system have been applied. Also, back up your existing installation, including all applications, configuration files, databases and database settings. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
    After
    Apache Log4j: Apache Log4j2 < 2.16.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CISA KEV ↗
  4. Affected versionsThe structured affected or fixed version information changed.
    Before
    Apache Log4j2 < 2.16.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    After
    Apache Log4j: Apache Log4j2 < 2.16.0 · Fixed: An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release.
    CNA ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Added to CISA KEV
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2021-34769↗Red Hat Product Security security advisory↗CISA KEV record↗Mitigation reference↗Mitigation reference↗Patch or update reference↗CVE authority or vendor reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2021-45046 · cve.blacktree.nl