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

Deserialization of untrusted data in JMSAppender in Apache Log4j 1.2

Apache Software Foundation · Apache Log4j 1.x

7.5HighCVSS 3.1
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 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 severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 80.60% 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 Log4j 1.x 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 13 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-log4j1.2Vendor fix publishedDebian records a fixed source-package version for this release.1.2.17-11Debian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourceapache-log4j1.2Vendor fix publishedDebian records a fixed source-package version for this release.1.2.17-11Debian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourceapache-log4j1.2Vendor fix publishedDebian records a fixed source-package version for this release.1.2.17-11Debian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourceapache-log4j1.2Vendor fix publishedDebian records a fixed source-package version for this release.1.2.17-11Debian Security Tracker ↗Source updated 5 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.

2 current
CVE-2021-4104 · CSAF 2.0 · revision 3 · finalRed Hat Product Securitylog4j: Remote code execution in Log4j 1.x when application is configured to use JMSAppender
7 known affected

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

  • log4j.src as a component of A-MQ Clients 2
  • log4j.src as a component of Red Hat AMQ Broker 7
  • log4j.src as a component of Red Hat JBoss Fuse Service Works 6
  • log4j.src as a component of Red Hat JBoss Operations Network 3
  • opendaylight as a component of Red Hat OpenStack Platform 13 (Queens)
  • opendaylight.src as a component of Red Hat OpenStack Platform 13 (Queens)
  • log4j.src as a component of streams for Apache Kafka
Summary
A flaw was found in the Java logging library Apache Log4j in version 1.x. JMSAppender in Log4j 1.x is vulnerable to deserialization of untrusted data. This allows a remote attacker to execute code on the server if the deployed application is configured to use JMSAppender and to the attacker's JNDI LDAP endpoint.
Remediation
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)
13 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 Eurotherm Data Reviewer software version 3.0.2 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
No remediation text is recorded.
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-2514

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

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 13 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

JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

What

JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

Why

Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.

What

JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

Why

Attacker-influenced serialised data is reconstructed as trusted objects, which can invoke dangerous application behaviour.

How

An attacker operating through a network path may attempt exploitation with low privileges. 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.
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 → Deserialization of Untrusted Data → execute code or commands in the affected security context
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
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-502 ↗

CWE-502: Deserialization of Untrusted Data. The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

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:L/UI:N/S:U/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.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's 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.
NetworkRemote code executionCWE-502
A

Official authority intelligence

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

BSI · German · WID-SEC-2026-2893Oracle Hyperion: Mehrere Schwachstellen

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

Official advisory ↗
BSI · German · WID-SEC-2024-1926Red Hat JBoss Enterprise Application Platform: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Red Hat JBoss Enterprise Application Platform auf Red Hat Enterprise Linux ausnutzen, um beliebigen Programmcode auszuführen, einen Denial-of-Service-Zustand zu erzeugen, vertrauliche Informationen preiszugeben, Dateien und Daten zu manipulieren oder Sicherheitsmaßnahmen zu umgehen.

Official advisory ↗
BSI · German · WID-SEC-2024-0794Dell ECS: Mehrere Schwachstellen

Ein Angreifer kann mehrere Schwachstellen in Dell ECS ausnutzen, um seine Privilegien zu erweitern, beliebigen Programmcode mit Administratorrechten auszuführen, Informationen offenzulegen, Dateien zu manipulieren, einen Cross-Site-Scripting-Angriff durchzuführen, Sicherheitsvorkehrungen zu umgehen oder einen Denial of Service Zustand herbeizuführen.

Official advisory ↗
BSI · German · WID-SEC-2024-0107Oracle Communications Applications: Mehrere Schwachstellen

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

Official advisory ↗
BSI · German · WID-SEC-2023-1807Oracle Fusion Middleware: Mehrere Schwachstellen

Ein Angreifer aus dem angrenzenden Netzwerk oder ein entfernter anonymer, authentisierter oder lokaler 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-0520Apache log4j: Schwachstelle ermöglicht Ausführen von beliebigem Programmcode

Ein entfernter, authentisierter Angreifer kann eine Schwachstelle in Apache log4j ausnutzen, um beliebigen Programmcode mit den Rechten des Dienstes auszuführen.

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

/CVERecord?id=CVE-2018-3823 Référence CVE CVE-2018-3824 https://www.cve.org/CVERecord?id=CVE-2018-3824 Référence CVE CVE-2018-3826 https://www.cve.org/CVERecord?id=CVE-2018-3826 Référence CVE CVE-2018-3831 https://www.cve.org/CVERecord?id=CVE-2018-3831 Référence CVE CVE-2019-12900 https://www.cve.org/CVERecord?id=CVE-2019-12900 Référence CVE CVE-2020-11023 https://www.cve.org/CVERecord?id=CVE-2020-11023 Référence CVE CVE-2021-22146 https://www.cve.org/CVERecord?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=C

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

port/pages/node/7152260 Référence CVE CVE-2017-16137 https://www.cve.org/CVERecord?id=CVE-2017-16137 Référence CVE CVE-2018-11770 https://www.cve.org/CVERecord?id=CVE-2018-11770 Référence CVE CVE-2018-11804 https://www.cve.org/CVERecord?id=CVE-2018-11804 Référence CVE CVE-2018-17190 https://www.cve.org/CVERecord?id=CVE-2018-17190 Référence CVE CVE-2019-17571 https://www.cve.org/CVERecord?id=CVE-2019-17571 Référence CVE CVE-2020-13936 https://www.cve.org/CVERecord?id=CVE-2020-13936 Référence CVE CVE-2020-9488 https://www.cve.org/CVERecord?id=CVE-2020-9488 Référence CVE CVE-2020-9493 https://www.cve.org/CVERecord?id=CVE-2020-9493 Référence CVE CVE-2021-4104 https://www.cve.org/CVERecord?id=CVE-2021-4104 Référence CVE CVE-2022-23302 https://www.cve.org/CVERecord?id=CVE-2022-23302 Référence CVE CVE-2022-23305 https://www.cve.org/CVERecord?id=CVE-2022-23305 Référence CVE CVE-2022-23307 https://www.cve.org/CVERecord?id=CVE-2022-23307 Référence CVE CVE-2022-25647 https://www.cve.org/CVERecord?id=CVE-2022-25647 Référence CVE CVE-2022-46751 https://www.cve.org/CVERecord?id=CVE-2022-46751 Référence CVE CVE-2023-22946 https://www.cve.org/CVERecord?id=CVE-2023-22946 Référence CVE CVE-2023-25613 https://www.cve.org/CVERecord?id=CVE-2023-25613 Référence CVE CVE-2023-26145 https://www.cve.org/CVERecord?id=C

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

CVERecord?id=CVE-2021-26691 Référence CVE CVE-2021-33655 https://www.cve.org/CVERecord?id=CVE-2021-33655 Référence CVE CVE-2021-33656 https://www.cve.org/CVERecord?id=CVE-2021-33656 Référence CVE CVE-2021-34798 https://www.cve.org/CVERecord?id=CVE-2021-34798 Référence CVE CVE-2021-3564 https://www.cve.org/CVERecord?id=CVE-2021-3564 Référence CVE CVE-2021-3573 https://www.cve.org/CVERecord?id=CVE-2021-3573 Référence CVE CVE-2021-3621 https://www.cve.org/CVERecord?id=CVE-2021-3621 Référence CVE CVE-2021-3752 https://www.cve.org/CVERecord?id=CVE-2021-3752 Référence CVE CVE-2021-39275 https://www.cve.org/CVERecord?id=CVE-2021-39275 Référence CVE CVE-2021-4104 https://www.cve.org/CVERecord?id=CVE-2021-4104 Référence CVE CVE-2021-4155 https://www.cve.org/CVERecord?id=CVE-2021-4155 Référence CVE CVE-2021-44228 https://www.cve.org/CVERecord?id=CVE-2021-44228 Référence CVE CVE-2021-44790 https://www.cve.org/CVERecord?id=CVE-2021-44790 Référence CVE CVE-2021-44832 https://www.cve.org/CVERecord?id=CVE-2021-44832 Référence CVE CVE-2022-0330 https://www.cve.org/CVERecord?id=CVE-2022-0330 Référence CVE CVE-2022-0934 https://www.cve.org/CVERecord?id=CVE-2022-0934 Référence CVE CVE-2022-1462 https://www.cve.org/CVERecord?id=CVE-2022-1462 Référence CVE CVE-2022-1679 https://www.cve.org/CVERecord?id=CVE-2022-1

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-0910Multiples vulnérabilités dans IBM QRadar

De multiples vulnérabilités ont été découvertes dans IBM QRadar. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un contournement de la politique de sécurité et une atteinte à l'intégrité des données.

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

rd?id=CVE-2017-7525 Référence CVE CVE-2018-11775 https://www.cve.org/CVERecord?id=CVE-2018-11775 Référence CVE CVE-2020-36518 https://www.cve.org/CVERecord?id=CVE-2020-36518 Référence CVE CVE-2021-35517 https://www.cve.org/CVERecord?id=CVE-2021-35517 Référence CVE CVE-2021-35550 https://www.cve.org/CVERecord?id=CVE-2021-35550 Référence CVE CVE-2021-35578 https://www.cve.org/CVERecord?id=CVE-2021-35578 Référence CVE CVE-2021-35603 https://www.cve.org/CVERecord?id=CVE-2021-35603 Référence CVE CVE-2021-36090 https://www.cve.org/CVERecord?id=CVE-2021-36090 Référence CVE CVE-2021-41035 https://www.cve.org/CVERecord?id=CVE-2021-41035 Référence CVE CVE-2021-4104 https://www.cve.org/CVERecord?id=CVE-2021-4104 Référence CVE CVE-2022-21248 https://www.cve.org/CVERecord?id=CVE-2022-21248 Référence CVE CVE-2022-21293 https://www.cve.org/CVERecord?id=CVE-2022-21293 Référence CVE CVE-2022-21294 https://www.cve.org/CVERecord?id=CVE-2022-21294 Référence CVE CVE-2022-21341 https://www.cve.org/CVERecord?id=CVE-2022-21341 Référence CVE CVE-2022-21434 https://www.cve.org/CVERecord?id=CVE-2022-21434 Référence CVE CVE-2022-21443 https://www.cve.org/CVERecord?id=CVE-2022-21443 Référence CVE CVE-2022-21496 https://www.cve.org/CVERecord?id=CVE-2022-21496 Référence CVE CVE-2022-23307 https://www.cve.org/CVERecord?id=C

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

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

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

De multiples vulnérabilités ont été découvertes dans IBM Spectrum. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, un contournement de la politique de sécurité et une atteinte à l'intégrité des données.

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

d?id=CVE-2021-22779 Référence CVE CVE-2021-22780 https://www.cve.org/CVERecord?id=CVE-2021-22780 Référence CVE CVE-2021-22781 https://www.cve.org/CVERecord?id=CVE-2021-22781 Référence CVE CVE-2021-22782 https://www.cve.org/CVERecord?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=C

Official advisory ↗
CERT-FR · French · CERTFR-2022-AVI-712Multiples vulnérabilités dans IBM QRadar SIEM

De multiples vulnérabilités ont été découvertes dans IBM QRadar SIEM. Elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance et un contournement de la politique de sécurité.

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-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-2022-AVI-056Multiples vulnérabilités dans Oracle WebLogic Server

ujan2022.html#AppendixFMW Référence CVE CVE-2018-1324 https://www.cve.org/CVERecord?id=CVE-2018-1324 Référence CVE CVE-2019-10219 https://www.cve.org/CVERecord?id=CVE-2019-10219 Référence CVE CVE-2020-11023 https://www.cve.org/CVERecord?id=CVE-2020-11023 Référence CVE CVE-2020-13956 https://www.cve.org/CVERecord?id=CVE-2020-13956 Référence CVE CVE-2020-2934 https://www.cve.org/CVERecord?id=CVE-2020-2934 Référence CVE CVE-2020-5258 https://www.cve.org/CVERecord?id=CVE-2020-5258 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-4104 https://www.cve.org/CVERecord?id=CVE-2021-4104 Référence CVE CVE-2021-44832 https://www.cve.org/CVERecord?id=CVE-2021-44832 Référence CVE CVE-2022-21252 https://www.cve.org/CVERecord?id=CVE-2022-21252 Référence CVE CVE-2022-21257 https://www.cve.org/CVERecord?id=CVE-2022-21257 Référence CVE CVE-2022-21258 https://www.cve.org/CVERecord?id=CVE-2022-21258 Référence CVE CVE-2022-21259 https://www.cve.org/CVERecord?id=CVE-2022-21259 Référence CVE CVE-2022-21260 https://www.cve.org/CVERecord?id=CVE-2022-21260 Référence CVE CVE-2022-21261 https://www.cve.org/CVERecord?id=CVE-2022-21261 Référence CVE CVE-2022-21262 https://www.cve.org/CVERecord?id=C

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

CVERecord?id=CVE-2021-30468 Référence CVE CVE-2021-34428 https://www.cve.org/CVERecord?id=CVE-2021-34428 Référence CVE CVE-2021-3536 https://www.cve.org/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

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2021-016230Log4j における信頼できないデータのデシリアライゼーションに関する脆弱性

Log4j には、信頼できないデータのデシリアライゼーションに関する脆弱性が存在します。 本脆弱性は、CVE-2021-44228 と関連する脆弱性です。

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
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 14 Dec 2021 · Last source change 28 May 2026, 19:53 UTC · CWE-502 · Deserialization of Untrusted Data

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-2514
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
    Apache Log4j 1.2 1.2.x · Fixed: No fixed version is explicitly recorded in the structured CVE data.
    After
    Apache Log4j 1.2 1.2.x · Fixed: 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. Remediation statusRemediation status changed from Awaiting fix to Patch available.
    Before
    Awaiting fix
    After
    Patch available
    Red Hat Product Security ↗
  3. Affected versionsThe structured affected or fixed version information changed.
    Before
    log4j.src as a component of A-MQ Clients 2; log4j.src as a component of Red Hat AMQ Broker 7; log4j.src as a component of Red Hat JBoss Fuse Service Works 6; log4j.src as a component of Red Hat JBoss Operations Network 3; opendaylight as a component of Red Hat OpenStack Platform 13 (Queens); opendaylight.src as a component of Red Hat OpenStack Platform 13 (Queens); log4j.src as a component of streams for Apache Kafka · Fixed: log4j-0:1.2.14-6.5.el6_10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-0:1.2.14-6.5.el6_10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-0:1.2.14-6.5.el6_10.src as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-0:1.2.14-6.5.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-debuginfo-0:1.2.14-6.5.el6_10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-debuginfo-0:1.2.14-6.5.el6_10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-debuginfo-0:1.2.14-6.5.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); jboss-as-appclient-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-appclient-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cli-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cli-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-client-all-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-client-all-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-clustering-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-clustering-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cmp-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cmp-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-configadmin-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-configadmin-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-connector-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-connector-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-client-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-client-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-core-security-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-core-security-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-deployment-repository-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-deployment-repository-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-deployment-scanner-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; and 550 more
    After
    log4j.src as a component of A-MQ Clients 2; log4j.src as a component of Red Hat AMQ Broker 7; log4j.src as a component of Red Hat JBoss Fuse Service Works 6; log4j.src as a component of Red Hat JBoss Operations Network 3; opendaylight as a component of Red Hat OpenStack Platform 13 (Queens); opendaylight.src as a component of Red Hat OpenStack Platform 13 (Queens); log4j.src as a component of streams for Apache Kafka · Fixed: log4j-0:1.2.14-6.5.el6_10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-0:1.2.14-6.5.el6_10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-0:1.2.14-6.5.el6_10.src as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-0:1.2.14-6.5.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-debuginfo-0:1.2.14-6.5.el6_10.i686 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-debuginfo-0:1.2.14-6.5.el6_10.s390x as a component of Red Hat Enterprise Linux Server (v. 6 ELS); log4j-debuginfo-0:1.2.14-6.5.el6_10.x86_64 as a component of Red Hat Enterprise Linux Server (v. 6 ELS); jboss-as-appclient-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-appclient-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cli-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cli-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-client-all-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-client-all-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-clustering-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-clustering-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cmp-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-cmp-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-configadmin-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-configadmin-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-connector-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-connector-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-client-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-controller-client-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-core-security-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-core-security-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-deployment-repository-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-deployment-repository-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.src as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; jboss-as-deployment-scanner-0:7.5.24-2.Final_redhat_00001.1.ep6.el6.noarch as a component of Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 Server; and 549 more
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release recorded from official guidance
Fixed release recorded from official guidance
Fixed release recorded from official guidance
ENISA EUVD · EUVD-2021-2514↗Red Hat Product Security security advisory↗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-4104 · cve.blacktree.nl