Skip to content
Vulnerability Intelligence

CVE-2021-4104

HighExploited

JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration.

Published Jun 20, 2022 · Updated Oct 5, 2026 · Also known as DEBIAN-CVE-2021-4104, DLA-2905-1, GHSA-fp5r-v3w9-4333, ROOT-APP-MAVEN-CVE-2021-4104, SUSE-SU-2021:14866-1, SUSE-SU-2021:4096-1, SUSE-SU-2021:4097-1, SUSE-SU-2021:4111-1, SUSE-SU-2021:4112-1, SUSE-SU-2021:4115-1, SUSE-SU-2021:4160-1, SUSE-SU-2021:4190-1, SUSE-SU-2022:0126-1, SUSE-SU-2022:0133-1, SUSE-SU-2022:0354-1, SUSE-SU-2022:0355-1, TR-21-1009, TR-21-1011, UBUNTU-CVE-2021-4104, USN-5223-1, USN-5223-2

Key Facts

Patch immediately
  • CVE-2021-4104 is a high-severity vulnerability (CVSS 7.5 v3.1) affecting Log4j (Apache), Advanced Supply Chain Planning (Oracle), Business Intelligence (Oracle) and 22 more products.
  • It is exploited in the wild, listed in Industry KEV feed since Apr 26, 2022. No public exploit code is known.
  • EPSS estimates a 81% probability of exploitation in the next 30 days.
  • Fixed versions are available, including apache-log4j1.2 1.2.17-10+deb11u1, apache-log4j1.2 1.2.17-11, apache-log4j1.2 1.2.17-4ubuntu3+esm1.
  • Brandefense priority: patch immediately, because it is listed as exploited in the wild.

CVSS v3.1

7.5

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

EPSS (30-day exploit likelihood)

81%

Higher than 99.6% of all scored CVEs

Exploited in the wild

Yes

1 catalog listing

Public exploit code

None known

Get the full CVE-2021-4104 brief as a PDF

Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.

Description

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.

Known-Exploited Catalog Listings

CatalogAddedRemediation dueRansomware use
Industry KEV feedApr 26, 2022n/aNot reported

Required action: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.

Affected Products

647 affected entries in total
ProductAffected versionsFixed in
Log4jApache1.21.2.17-16.12.amzn1
Advanced Supply Chain PlanningOracle12.1, 12.2n/a
Business IntelligenceOracle12.2.1.3.0, 12.2.1.4.0, 5.9.0.0.0n/a
Business Process Management SuiteOracle12.2.1.3.0, 12.2.1.4.0n/a
Communications Eagle FTP Table Base RetrievalOracle4.5n/a
20 more affected products in the full CVE brief

Patched Releases

apache-log4j1.2

1.2.17-10+deb11u1, 1.2.17-11, 1.2.17-4ubuntu3+esm1, 1.2.17-7+deb9u2, 1.2.17-7ubuntu1+esm1, 1.2.17-8+deb10u1ubuntu0.1, 1.2.17-9ubuntu0.1

chainsaw

1.2.17-5.1

druid

35.0.1-r1

eap7-apache-cxf

0:3.4.10-1.SP1_redhat_00001.1.el7eap

eap7-avro

0:1.7.6-8.redhat_00003.1.el7eap

eap7-h2database

0:1.4.197-3.redhat_00004.1.el7eap

eap7-jboss-annotations-api_1.3_spec

0:2.0.1-4.Final_redhat_00001.1.el7eap

eap7-jboss-marshalling

0:2.0.15-1.Final_redhat_00001.1.el7eap

eap7-jboss-server-migration

0:1.7.2-12.Final_redhat_00013.1.el7eap

eap7-jboss-xnio-base

0:3.7.13-1.Final_redhat_00001.1.el7eap

eap7-log4j

0:2.17.1-1.redhat_00001.1.el7eap, 0:2.17.1-1.redhat_00001.1.el8eap

eap7-log4j-jboss-logmanager

0:1.2.2-1.Final_redhat_00002.1.el8eap, 0:1.2.2-1.Final_redhat_00002.1.ep7.el7

eap7-wildfly

0:7.3.11-4.GA_redhat_00002.1.el7eap

eap7-wss4j

0:2.3.3-2.redhat_00001.1.el7eap

eap7-xalan-j2

0:2.7.1-38.redhat_00015.1.el7eap

eap7-xml-security

0:2.2.3-2.redhat_00001.1.el7eap

elasticsearch

2.4.2-5.3.1, 2.4.2-5.6.1, 2.4.2-6.3.1, 2.4.2-6.6.1

io.root.log4j:log4j

1.2.12-root.io.1, 1.2.12-root.io.2, 1.2.14-root.io.2, 1.2.14-root.io.3, 1.2.14-root.io.4, 1.2.14-root.io.5, 1.2.14-root.io.6

jboss-as-appclient

0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7

jboss-as-cli

0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7

jboss-as-client-all

0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7

jboss-as-clustering

0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7

jboss-as-cmp

0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7

jboss-as-configadmin

0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7

jboss-as-connector

0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7

Timeline

  1. Added to Industry KEV feed

    Apr 26, 2022

  2. Publicly disclosed

    Jun 20, 2022

  3. Last updated

    Oct 5, 2026

Weakness Type

  • CWE-20 Improper Input Validation
  • CWE-502 Deserialization of Untrusted Data

References

15 more references in the full CVE brief

FAQ

Common Questions.

Is CVE-2021-4104 Running On Your Attack Surface?

Brandefense maps vulnerabilities like this one to your internet-facing assets and tells you exactly where to patch.

Request A Demo