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

Apache Log4j2 does not always protect from infinite recursion in lookup evaluation

Apache Software Foundation · Apache Log4j2

5.9MediumCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 6 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 severityMediumOperational priority:High, raised one band.upgradedsince 5 Oct 2026

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 100.00% 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.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Apache Software Foundation 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 30 daysRemediation target: Within 180 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 6 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.17.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.17.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.17.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.17.0-1Debian Security Tracker ↗Source updated 6 Oct 2026
Open-source package ranges7 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-core>= 2.4.0, < 2.12.32.12.3GitHub advisory ↗github reviewed aggregator · 9 Jun 2026
mavenorg.apache.logging.log4j:log4j-core>= 2.13.0, < 2.17.02.17.0GitHub advisory ↗github reviewed aggregator · 9 Jun 2026
mavenorg.apache.logging.log4j:log4j-core< 2.3.12.3.1GitHub advisory ↗github reviewed aggregator · 9 Jun 2026
mavenorg.ops4j.pax.logging:pax-logging-log4j2>= 1.8.0, < 1.9.21.9.2GitHub advisory ↗github reviewed aggregator · 9 Jun 2026
mavenorg.ops4j.pax.logging:pax-logging-log4j2>= 1.10.0, < 1.10.91.10.9GitHub advisory ↗github reviewed aggregator · 9 Jun 2026
mavenorg.ops4j.pax.logging:pax-logging-log4j2>= 1.11.0, < 1.11.121.11.12GitHub advisory ↗github reviewed aggregator · 9 Jun 2026
mavenorg.ops4j.pax.logging:pax-logging-log4j2>= 2.0.0, < 2.0.132.0.13GitHub advisory ↗github reviewed aggregator · 9 Jun 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.

4 current
CVE-2021-45105 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitylog4j-core: DoS in log4j 2.x with Thread Context Map (MDC) input data contains a recursive lookup and context lookup pattern
4 known affected

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

  • log4j-api as a component of Red Hat Decision Manager 7
  • log4j-core as a component of Red Hat Integration Camel Quarkus 1
  • openshift3/ose-logging-elasticsearch5 as a component of Red Hat OpenShift Container Platform 3.11
  • log4j-core as a component of streams for Apache Kafka
Summary
A flaw was found in the Apache Log4j logging library 2.x. when the logging configuration uses a non-default Pattern Layout with a Context Lookup. Attackers with control over Thread Context Map (MDC) input data can craft malicious input data that contains a recursive lookup and can cause Denial of Service.
Remediation
Before applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. For details on how to apply this update, which includes the changes described in this advisory, 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)
2 known affected

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

  • 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-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
Apache Log4j2 versions 2.0-alpha1 through 2.16.0 did not protect from uncontrolled recursion from self-referential lookups, 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 that contains a recursive lookup, resulting in a denial of service condition.
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-501673 · CSAF 2.0 · revision 1 · interimSiemens ProductCERTSSA-501673: Apache Log4j Denial of Service Vulnerability (CVE-2021-45105) - Impact to Siemens Products
1 known affected

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

  • No product currently identified as affected
Summary
Apache Log4j2 versions 2.0-alpha1 through 2.16.0 did not protect from uncontrolled recursion from self-referential lookups, 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 that contains a recursive lookup, resulting in a denial of service condition.
Remediation
The table will be updated in case vulnerable products become known.
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-2559

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

Medium technical severity with no CISA KEV confirmation; remediate through the normal risk-based patch cycle unless local exposure raises the priority. Verified remediation exists for at least one product or source, but 6 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 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.

What

Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

What

Apache Log4j2 versions 2.0-alpha1 through 2.16.0 (excluding 2.12.3 and 2.3.1) did not protect from uncontrolled recursion from self-referential lookups. This allows an attacker with control over Thread Context Map data to cause a denial of service when a crafted string is interpreted. This issue was fixed in Log4j 2.17.0, 2.12.3, and 2.3.1.

Why

The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may disrupt the affected service.

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.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

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 Input Validation → disrupt the affected service
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-20 ↗

CWE-20: Improper Input Validation. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

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:U/C:N/I:N/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.SUnchangedScope: The security impact remains within the vulnerable component's authority.CNoneConfidentiality impact: No direct loss is represented by this metric.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedDenial of serviceCWE-20
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-0162Oracle 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-0119Oracle Utilities Applications: Mehrere Schwachstellen

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

Official advisory ↗
BSI · German · WID-SEC-2022-0811Apache log4j: Schwachstelle ermöglicht Denial of Service

Ein entfernter, anonymer Angreifer kann eine Schwachstelle in Apache log4j ausnutzen, um einen Denial of Service Angriff durchzufü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-20211222Security Bulletin 22 Dec 2021

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 22 Dec 2021, published on 22 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

cord?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=CVE-2022-48622 Référence CVE CVE-2023-0464 https://www.cve.org/CVERecord?id=C

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-0756Multiples vulnérabilités dans les produits VMware

CVERecord?id=CVE-2021-35942 Référence CVE CVE-2021-38604 https://www.cve.org/CVERecord?id=CVE-2021-38604 Référence CVE CVE-2021-3875 https://www.cve.org/CVERecord?id=CVE-2021-3875 Référence CVE CVE-2021-3999 https://www.cve.org/CVERecord?id=CVE-2021-3999 Référence CVE CVE-2021-4122 https://www.cve.org/CVERecord?id=CVE-2021-4122 Référence CVE CVE-2021-4193 https://www.cve.org/CVERecord?id=CVE-2021-4193 Référence CVE CVE-2021-43618 https://www.cve.org/CVERecord?id=CVE-2021-43618 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-45105 https://www.cve.org/CVERecord?id=CVE-2021-45105 Référence CVE CVE-2021-46848 https://www.cve.org/CVERecord?id=CVE-2021-46848 Référence CVE CVE-2022-0213 https://www.cve.org/CVERecord?id=CVE-2022-0213 Référence CVE CVE-2022-0396 https://www.cve.org/CVERecord?id=CVE-2022-0396 Référence CVE CVE-2022-0635 https://www.cve.org/CVERecord?id=CVE-2022-0635 Référence CVE CVE-2022-0667 https://www.cve.org/CVERecord?id=CVE-2022-0667 Référence CVE CVE-2022-1271 https://www.cve.org/CVERecord?id=CVE-2022-1271 Référence CVE CVE-2022-1292 https://www.cve.org/CVERecord?id=CVE-2022-1292 Référence CVE CVE-2022-1473 https://www.cve.org/CVERecord?id=CVE-2022-1473

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

ord?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=CVE-2022-34765 Référence CVE CVE-2022-37300 https://www.cve.org/CVERecord?id=

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

Record?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-27774 Référence CVE CVE-2022-27775 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

cord?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-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 ↗
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 ↗
KISA KrCERT/CC · Korean · KNVD-5487설 연휴기간 사이버 공격 대비 보안 권고 사항 (상세)

확인적용 ② 기본 원격포트(22. 3389) 사용을 자제하고, OTP 등을 통한 추가 인증 강화 ③ VPN 장비를 운영하는 경우, 허가된 사용자와 단말기만 업무망에 접근할 수 있도록 설정하고 OTP 등을 통한 추가 인증 강화 ④ 다수의 서버를 운영하는 경우 내부 서버 간 원격접속이 불가능 하도록 접근 제어 설정 ⑤ AD 인프라를 운영 중인 기업의 경우, 관리자 그룹 계정의 최소화 및 관련 PC의 인터넷망 분리 운영 ⑥ 주요 관리자 PC에 대한 주기적인 보안 점검 및 인터넷망 분리 운영 ⑦ 외부에 오픈된 DB서비스(MSSQL, MYSQL 등) 접근을 차단하고, 불필요하게 외부에 오픈된 원격 접속 서비스 접근 차단 ⑧ DB 최초 설치 시 기본 관리자 패스워드는 반드시 변경 후 사용하고, 사용하지 않는 계정 비활성화 ⑨ 가상머신 운영환경을 타깃으로 하는 리눅스용 랜섬웨어 공격이 발생하고 있으니 백업 및 운영체계 강화 ☞ 특히 아래의 취약점을 이용하여 해킹사고가 발생 할 수 있으니 반드시 보안 업데이트 등 조치 필요 (1) MS 윈도우 Exchange 서버 취약점 보안 업데이트 권고 (CVE-2021-26855, 26857, 27065, 26585, 27065, 31207, 34473, 34523) (2) Apache Log4j 보안 업데이트 권고 (CVE-2021-45105, 44832, CVE-2022-23302, 23305, 23307) o PC 보안 강화 방안 ① 피싱 메일에 주의하고 본문 링크 클릭, 첨부파일 다운로드, 실행에 주의 ② 매월 운영체제 및 주요 프로그램(웹브라우저, Flash, Java 등)의 보안 업데이트 확인적용 ③ 상용 메일을 통한 주요 업무 자료 송수신 금지 ※ 불가피한 경우, OTP 설정 및 허가된 사용자 단말기 추가 등을 통해 인증 강화 ④ 웹하드·P2P 사이트를 통한 불법 다운로드 금지 o NAS 보안 강화 방안 ① 최초 설치 시 기본 관리자 패스워드는 반드시 변경 후 사용 ② 자동 업데이트를 활성화하여 최신 펌웨어 유지 ③ 인터넷을 통한 직접 접속은 차단하고, 사내망에서 운영 권고 ※ 불가피한 경우, 장비의 비밀번호 관리 및 백업, 보안 업데이트 등 철저한 관리 필요 o IoT 보안 강화 방안 ① 관리자 페이지 초기 설정 비밀번호 변경 후 사용 ② 불필요한 SSH 등 포트 사용 중지 ※ 불가피한 경우, 장비의 로그인 계정 변경(관리자 로그인 계정과 다른 값으로 설정) ☞ 특히 IP카메라, LTE모뎀, DVR 제품의 경우 필수적으로 조치 필요 o 공통 보안 강화 방안 ① 사용하지 않는 시스템은 전원을 종료하여 해킹 경로로 활용되는 것을 사전 방지 ② 중요 파일 및 문서 등은 네트워

Official advisory ↗
KISA KrCERT/CC · Korean · KNVD-5474Apache Log4j 보안 업데이트 권고(CVE-2021-45105, 44832, CVE-2022-23302, 23305, 23307) (Update. 22-1-21 17:00)

#### Apache Log4j 보안 업데이트 권고(CVE-2021-45105, 44832, CVE-2022-23302, 23305, 23307) (Update. 22-1-21 17:00) 2021.12.18 2021-12-18 : CVE-2021-45105 취약점 보안 업데이트 2021-12-20 : 조치방안 내 오타 수정 2021-12-22 : 대응방안 업데이트(Java 6, 7 대상) 2021-12-29 : CVE-2021-44832 취약점 보안 업데이트 2021-12-30 : Log4j 2.12.4, 2.3.2 다운로드 추가 2021-12-31 : 영향을 받는 부분 수정 2022-1-3 : 영향받는 버전 수정 2022-1-21 : CVE-2022-23302, 23305, 23307 취약점 관련 내용 추가 ##### □ 개요 o Apache 소프트웨어 재단은 자사의 Log4j에서 발생하는 취약점을 해결한 보안 업데이트 권고[1] o 공격자는 해당 취약점을 이용하여 정상 서비스 중지 등의 피해를 발생시킬수 있으므로, 최신 버전으로 업데이트 권고 ※ Log4j 취약점을 이용한 침해사고 발생시 한국인터넷진흥원에 신고해 주시기 바랍니다. ##### □ 주요 내용 o Apache Log4j 2에서 발생하는 서비스 거부 취약점(CVE-2021-45105)[2] o Apache Log4j 2에서 발생하는 원격코드 실행 취약점(C

Official advisory ↗
NCSC-NL · Dutch · NCSC-2026-0027Kwetsbaarheden verholpen in Oracle Fusion Middleware

Multiple vulnerabilities across Apache Log4j, Oracle products, and various dependencies expose systems to denial-of-service and remote code execution risks, necessitating updates to secure versions.

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 18 Dec 2021 · Last source change 29 May 2026, 11:45 UTC · CWE-20 · Improper Input Validation

CVE recordCVE.org · 5.2
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-2559
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment

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
    log4j-core < 2.17.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
    log4j-core < 2.17.0 · Fixed: Before applying this update, back up your existing Red Hat JBoss Enterprise Application Platform installation and deployed applications. For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    log4j-api as a component of Red Hat Decision Manager 7; log4j-core as a component of Red Hat Integration Camel Quarkus 1; openshift3/ose-logging-elasticsearch5 as a component of Red Hat OpenShift Container Platform 3.11; log4j-core as a component of streams for Apache Kafka · Fixed: eap7-log4j-0:2.17.1-1.redhat_00001.1.el7eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 7 Server; eap7-log4j-0:2.17.1-1.redhat_00001.1.el7eap.src as a component of Red Hat JBoss EAP 7.4 for RHEL 7 Server; rh-sso7-keycloak-0:15.0.6-1.redhat_00001.1.el7sso.noarch as a component of Red Hat Single Sign-On 7.5 for RHEL 7 Server; rh-sso7-keycloak-0:15.0.6-1.redhat_00001.1.el7sso.src as a component of Red Hat Single Sign-On 7.5 for RHEL 7 Server; rh-sso7-keycloak-server-0:15.0.6-1.redhat_00001.1.el7sso.noarch as a component of Red Hat Single Sign-On 7.5 for RHEL 7 Server; eap7-log4j-0:2.17.1-1.redhat_00001.1.el8eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 8; eap7-log4j-0:2.17.1-1.redhat_00001.1.el8eap.src as a component of Red Hat JBoss EAP 7.4 for RHEL 8; openshift-logging/elasticsearch6-rhel8@sha256:000b9988602eae29b14b0dfe62b5da73ded51fcd2dd634c6436b23bceb3e4bb5_amd64 as a component of OpenShift Logging 5.0; openshift-logging/elasticsearch6-rhel8@sha256:339b7a228a8cd1e15498a6081332ec0af20913f488afa521e5134bf78f6eb6f3_s390x as a component of OpenShift Logging 5.0; openshift-logging/elasticsearch6-rhel8@sha256:7aca3211b51bcddcfb1e821fa45db1f05ef466e225ccc9b56ae5ebc9ab10ad8d_ppc64le as a component of OpenShift Logging 5.0; openshift-logging/elasticsearch6-rhel8@sha256:0bda3c71be7183afc13247ae55ca2f5b11193a82c8440a883aa73e403b5f77f6_ppc64le as a component of OpenShift Logging 5.1; openshift-logging/elasticsearch6-rhel8@sha256:74bc681d8c448a4bdff547b3f8119028e904c64c710fb1b5bb4ee016b13c2fdc_s390x as a component of OpenShift Logging 5.1; openshift-logging/elasticsearch6-rhel8@sha256:fef623d868f3c6f16d39f1853e236e52fbdf48f529b8fec4db21301d4fabecd5_amd64 as a component of OpenShift Logging 5.1; openshift-logging/elasticsearch6-rhel8@sha256:3b1f2a711ff8e9c7df0ae2f40bf9c700f559b6027c6a2cacaf15f016fea61083_ppc64le as a component of OpenShift Logging 5.2; openshift-logging/elasticsearch6-rhel8@sha256:40992ca8e55a2c4508095c1c8d69f2db6c44a498de1a679e82f2d602977f8b92_amd64 as a component of OpenShift Logging 5.2; openshift-logging/elasticsearch6-rhel8@sha256:64d4e40746eee55b9c5b3a8ea51fac27e4d279cc9ded536983f3d8c682c787b6_s390x as a component of OpenShift Logging 5.2; openshift-logging/elasticsearch6-rhel8@sha256:2208f64bdb5b79cd18bdc79ad9d788a0063581b8e60bed0f914ea3bd19011fc5_amd64 as a component of OpenShift Logging 5.3; openshift-logging/elasticsearch6-rhel8@sha256:d927a7bc1d652d75fa215cd9beceb1ccd6798acf85aeebd1e1c7d16c33f2dfa8_ppc64le as a component of OpenShift Logging 5.3; openshift-logging/elasticsearch6-rhel8@sha256:ea2783491c18252fe152eeb2799dfee17700cbc613b0a519ea8e69c6dcbb7984_s390x as a component of OpenShift Logging 5.3; openshift4/ose-logging-elasticsearch6@sha256:169e6882974d9cd36d72e1db75b57071aca7b8cf5aa2c13c8f7e3157505b80c3_ppc64le as a component of Red Hat OpenShift Container Platform 4.6; openshift4/ose-logging-elasticsearch6@sha256:29643626fe608c5ff0ea815a0afaed3fe7112f6c50963991014542cdb7ece835_s390x as a component of Red Hat OpenShift Container Platform 4.6; openshift4/ose-logging-elasticsearch6@sha256:f1a53e3be27c714226869b259c8eed80ac797b0cb83fbc2d786a9bba383d9547_amd64 as a component of Red Hat OpenShift Container Platform 4.6; rh-sso7-keycloak-0:15.0.6-1.redhat_00001.1.el8sso.noarch as a component of Red Hat Single Sign-On 7.5 for RHEL 8; rh-sso7-keycloak-0:15.0.6-1.redhat_00001.1.el8sso.src as a component of Red Hat Single Sign-On 7.5 for RHEL 8; rh-sso7-keycloak-server-0:15.0.6-1.redhat_00001.1.el8sso.noarch as a component of Red Hat Single Sign-On 7.5 for RHEL 8; Red Hat AMQ Streams 1.6.6; Red Hat Data Grid 8.2.3; Red Hat Fuse 7.8.2, 7.9.1, 7.10.1; Red Hat Integration Camel Extensions for Quarkus 2.2; Red Hat Integration Camel-K 1.6.3; and 4 more
    After
    log4j-api as a component of Red Hat Decision Manager 7; log4j-core as a component of Red Hat Integration Camel Quarkus 1; openshift3/ose-logging-elasticsearch5 as a component of Red Hat OpenShift Container Platform 3.11; log4j-core as a component of streams for Apache Kafka · Fixed: eap7-log4j-0:2.17.1-1.redhat_00001.1.el7eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 7 Server; eap7-log4j-0:2.17.1-1.redhat_00001.1.el7eap.src as a component of Red Hat JBoss EAP 7.4 for RHEL 7 Server; rh-sso7-keycloak-0:15.0.6-1.redhat_00001.1.el7sso.noarch as a component of Red Hat Single Sign-On 7.5 for RHEL 7 Server; rh-sso7-keycloak-0:15.0.6-1.redhat_00001.1.el7sso.src as a component of Red Hat Single Sign-On 7.5 for RHEL 7 Server; rh-sso7-keycloak-server-0:15.0.6-1.redhat_00001.1.el7sso.noarch as a component of Red Hat Single Sign-On 7.5 for RHEL 7 Server; eap7-log4j-0:2.17.1-1.redhat_00001.1.el8eap.noarch as a component of Red Hat JBoss EAP 7.4 for RHEL 8; eap7-log4j-0:2.17.1-1.redhat_00001.1.el8eap.src as a component of Red Hat JBoss EAP 7.4 for RHEL 8; openshift-logging/elasticsearch6-rhel8@sha256:000b9988602eae29b14b0dfe62b5da73ded51fcd2dd634c6436b23bceb3e4bb5_amd64 as a component of OpenShift Logging 5.0; openshift-logging/elasticsearch6-rhel8@sha256:339b7a228a8cd1e15498a6081332ec0af20913f488afa521e5134bf78f6eb6f3_s390x as a component of OpenShift Logging 5.0; openshift-logging/elasticsearch6-rhel8@sha256:7aca3211b51bcddcfb1e821fa45db1f05ef466e225ccc9b56ae5ebc9ab10ad8d_ppc64le as a component of OpenShift Logging 5.0; openshift-logging/elasticsearch6-rhel8@sha256:0bda3c71be7183afc13247ae55ca2f5b11193a82c8440a883aa73e403b5f77f6_ppc64le as a component of OpenShift Logging 5.1; openshift-logging/elasticsearch6-rhel8@sha256:74bc681d8c448a4bdff547b3f8119028e904c64c710fb1b5bb4ee016b13c2fdc_s390x as a component of OpenShift Logging 5.1; openshift-logging/elasticsearch6-rhel8@sha256:fef623d868f3c6f16d39f1853e236e52fbdf48f529b8fec4db21301d4fabecd5_amd64 as a component of OpenShift Logging 5.1; openshift-logging/elasticsearch6-rhel8@sha256:3b1f2a711ff8e9c7df0ae2f40bf9c700f559b6027c6a2cacaf15f016fea61083_ppc64le as a component of OpenShift Logging 5.2; openshift-logging/elasticsearch6-rhel8@sha256:40992ca8e55a2c4508095c1c8d69f2db6c44a498de1a679e82f2d602977f8b92_amd64 as a component of OpenShift Logging 5.2; openshift-logging/elasticsearch6-rhel8@sha256:64d4e40746eee55b9c5b3a8ea51fac27e4d279cc9ded536983f3d8c682c787b6_s390x as a component of OpenShift Logging 5.2; openshift-logging/elasticsearch6-rhel8@sha256:2208f64bdb5b79cd18bdc79ad9d788a0063581b8e60bed0f914ea3bd19011fc5_amd64 as a component of OpenShift Logging 5.3; openshift-logging/elasticsearch6-rhel8@sha256:d927a7bc1d652d75fa215cd9beceb1ccd6798acf85aeebd1e1c7d16c33f2dfa8_ppc64le as a component of OpenShift Logging 5.3; openshift-logging/elasticsearch6-rhel8@sha256:ea2783491c18252fe152eeb2799dfee17700cbc613b0a519ea8e69c6dcbb7984_s390x as a component of OpenShift Logging 5.3; openshift4/ose-logging-elasticsearch6@sha256:169e6882974d9cd36d72e1db75b57071aca7b8cf5aa2c13c8f7e3157505b80c3_ppc64le as a component of Red Hat OpenShift Container Platform 4.6; openshift4/ose-logging-elasticsearch6@sha256:29643626fe608c5ff0ea815a0afaed3fe7112f6c50963991014542cdb7ece835_s390x as a component of Red Hat OpenShift Container Platform 4.6; openshift4/ose-logging-elasticsearch6@sha256:f1a53e3be27c714226869b259c8eed80ac797b0cb83fbc2d786a9bba383d9547_amd64 as a component of Red Hat OpenShift Container Platform 4.6; rh-sso7-keycloak-0:15.0.6-1.redhat_00001.1.el8sso.noarch as a component of Red Hat Single Sign-On 7.5 for RHEL 8; rh-sso7-keycloak-0:15.0.6-1.redhat_00001.1.el8sso.src as a component of Red Hat Single Sign-On 7.5 for RHEL 8; rh-sso7-keycloak-server-0:15.0.6-1.redhat_00001.1.el8sso.noarch as a component of Red Hat Single Sign-On 7.5 for RHEL 8; Red Hat AMQ Streams 1.6.6; Red Hat Data Grid 8.2.3; Red Hat Fuse 7.8.2, 7.9.1, 7.10.1; Red Hat Integration Camel Extensions for Quarkus 2.2; Red Hat Integration Camel-K 1.6.3; and 3 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2021-2559↗Red Hat Product Security security advisory↗CVE authority or vendor reference↗Mitigation reference↗Patch or update reference↗Patch or update 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-45105 · cve.blacktree.nl