CVE-2022-23302
HighDeserialization of Untrusted Data in Log4j 1.x
Published Jan 21, 2022 · Updated Oct 8, 2026 · Also known as DEBIAN-CVE-2022-23302, GHSA-w9p3-5cr8-m3jj, ROOT-APP-MAVEN-CVE-2022-23302, SUSE-SU-2022:0212-1, SUSE-SU-2022:0214-1, SUSE-SU-2022:0226-1, SUSE-SU-2022:14881-1, UBUNTU-CVE-2022-23302, USN-7590-1
Key Facts
Patch immediately- CVE-2022-23302 is a high-severity vulnerability (CVSS 8.8 v3.1) affecting Log4j (Apache), Brocade Sannav (Broadcom), Snapmanager (Netapp) and 22 more products.
- It is not listed in any known-exploited vulnerabilities catalog. No public exploit code is known.
- EPSS estimates a 64% probability of exploitation in the next 30 days.
- Fixed versions are available, including Log4j <=1.2.17, Log4j 0:1.2.14-6.6.el6_10, Log4j 0:1.2.17-18.el7_4.
- Brandefense priority: patch immediately, because it is very likely to be exploited soon.
CVSS v3.1
8.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (30-day exploit likelihood)
64%
Higher than 99.2% of all scored CVEs
Exploited in the wild
No known
Not in a known-exploited catalog
Public exploit code
None known
Get the full CVE-2022-23302 brief as a PDF
Every affected product and fixed release, exploitation status and a first 24 hours response checklist, emailed within minutes.
Description
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to. The attacker can provide a TopicConnectionFactoryBindingName configuration causing JMSSink to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-4104. Note this issue only affects Log4j 1.x when specifically configured to use JMSSink, 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.
Affected Products
625 affected entries in total| Product | Affected versions | Fixed in |
|---|---|---|
| Log4jApache | See advisory | 1.2.17 |
| Brocade SannavBroadcom | See advisory | n/a |
| SnapmanagerNetapp | See advisory | n/a |
| Advanced Supply Chain PlanningOracle | 12.1, 12.2 | n/a |
| Business IntelligenceOracle | 12.2.1.3.0, 12.2.1.4.0, 5.9.0.0.0 | n/a |
Patched Releases
Log4j
<=1.2.17, 0:1.2.14-6.6.el6_10, 0:1.2.17-18.el7_4, 1.2.14-6.4.2.el6_10, 1.2.15-126.9.1, 1.2.15-26.32.20.1, 1.2.17-16.14.amzn1, 1.2.17-18.amzn2, 1.2.17-18.el7_4, 1.2.17-5.9.1
Apache Log4j 1.x
2.0-alpha1, unspecified
apache-log4j1.2
1.2.17-10+deb11u1, 1.2.17-11, 1.2.17-4ubuntu3+esm2, 1.2.17-7+deb9u2, 1.2.17-7ubuntu1+esm1, 1.2.17-8+deb10u1ubuntu0.2, 1.2.17-9ubuntu0.2
druid
35.0.1-r1
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
elasticsearch
2.4.2-5.6.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.1, 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
jboss-as-controller
0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7
jboss-as-controller-client
0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7
jboss-as-core-security
0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7
jboss-as-deployment-repository
0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7
jboss-as-deployment-scanner
0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7
jboss-as-domain-http
0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7
jboss-as-domain-management
0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7
jboss-as-ee
0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7
jboss-as-ee-deployment
0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7
jboss-as-ejb3
0:7.5.24-2.Final_redhat_00001.1.ep6.el6, 0:7.5.24-2.Final_redhat_00001.1.ep6.el7
Timeline
Publicly disclosed
Jan 21, 2022
Last updated
Oct 8, 2026
Weakness Type
- CWE-502 Deserialization of Untrusted Data
References
- advisoryRHSA-2022:0289
- advisoryRHSA-2022:0290
- advisoryRHSA-2022:0291
- advisoryRHSA-2022:0294
- advisoryRHSA-2022:0430
FAQ
Common Questions.
JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration or if the configuration references an LDAP service the attacker has access to.
Affected: Log4j (Apache); Brocade Sannav (Broadcom); Snapmanager (Netapp), among others. The full list is in the CVE brief.
It is not listed in any known-exploited vulnerabilities catalog.
No, it is not currently listed in the CISA Known Exploited Vulnerabilities catalog.
No public exploit code is known.
Fixed versions are available, including Log4j <=1.2.17, Log4j 0:1.2.14-6.6.el6_10, Log4j 0:1.2.17-18.el7_4.
Brandefense priority: patch immediately, because it is very likely to be exploited soon.
Is CVE-2022-23302 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