CVE-2022-23302

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2022-01-21. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, nvd
Elevated
8.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 62%
CISA-KEV: Not listedEPSS: 62%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
99.1%
KEV
Not listed

Published

January 18, 2022

Last Modified

May 27, 2026

Advisory Details (4)

Auto-updated May 22, 2026
No patch confirmed yet.
generic

NetApp Product Security

https://security.netapp.com/advisory/ntap-20220217-0006/
generic

Apache log4j 1.2 -

https://logging.apache.org/log4j/1.2/index.html
generic
https://lists.apache.org/thread/bsr3l5qz4g0myrjhy9h67bcxodpkwj4w
generic

oss-security - CVE-2022-23302: Deserialization of untrusted data in JMSSink in Apache Log4j 1.x

http://www.openwall.com/lists/oss-security/2022/01/18/3

Vendor Advisories for CVE-2022-23302(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(22)

Vendor / EcosystemFixed in / PatchReleasedSource
redhateap7-log4j-jboss-logmanager-0:1.2.2-1.Final_redhat_00002.1.ep7.el72024-08-26redhat
redhatpatch2022-06-30redhat
redhatjbossweb-0:7.5.32-2.Final_redhat_1.2.ep6.el72022-06-30redhat
redhatjbossweb-0:7.5.32-2.Final_redhat_1.2.ep6.el62022-06-30redhat
redhateap7-log4j-0:2.17.1-1.redhat_00001.1.el8eap2022-04-11redhat
redhateap7-log4j-0:2.17.1-1.redhat_00001.1.el7eap2022-04-11redhat
redhatlog4j2022-04-11redhat
redhattomcat-native-0:1.2.23-26.redhat_26.ep7.el72022-02-14redhat
redhatlog4j-eap62022-02-14redhat
redhatpatch2022-02-08redhat
redhatsnmp4j-0:3.6.4-0.1.el8ev2022-02-08redhat
redhatrh-sso-7/sso7-rhel8-operator-bundle:7.5.1-92022-02-07redhat
redhatrh-sso7-keycloak-0:15.0.4-1.redhat_00003.1.el7sso2022-02-07redhat
redhatrh-sso-7/sso74-openj9-openshift-rhel8:7.4-602022-02-07redhat
redhatlog4j-0:1.2.17-18.el7_42022-02-07redhat
redhatrh-sso7-keycloak-0:15.0.4-1.redhat_00003.1.el8sso2022-02-07redhat
redhatrh-sso-7/sso74-openshift-rhel8:7.4-452022-02-07redhat
redhateap7-log4j-jboss-logmanager-0:1.2.2-1.Final_redhat_00002.1.el7eap2022-02-03redhat
redhatrh-maven36-log4j12-0:1.2.17-23.4.el72022-02-03redhat
redhatlog4j-jboss-logmanager-0:1.1.4-3.Final_redhat_00002.1.ep6.el72022-02-03redhat
mavenlog4j:log4j—ghsa
mavenorg.zenframework.z8.dependencies.commons:log4j-1.2.17—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
log4j:log4j1.1.3 ... 1.2.9 (14 versions)——
org.zenframework.z8.dependencies.commons:log4j-1.2.172.0——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(14)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 6× in last 7d / 32× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:25 UTCEPSS rescore
  2. 2026-07-09 19:07 UTCEPSS rescore
  3. 2026-07-08 15:12 UTCEPSS rescore
  4. 2026-07-06 16:25 UTCEPSS rescore
  5. 2026-07-06 16:25 UTCEPSS rescore
  6. 2026-07-05 02:28 UTCEPSS rescore
  7. 2026-07-01 15:04 UTCEPSS rescore
  8. 2026-06-28 04:54 UTCEPSS rescore
  9. 2026-06-28 04:54 UTCEPSS rescore
  10. 2026-06-27 03:07 UTCEPSS rescore
  11. 2026-06-25 13:48 UTCEPSS rescore
  12. 2026-06-24 14:03 UTCEPSS rescore
  13. 2026-06-24 14:03 UTCEPSS rescore
  14. 2026-06-23 21:31 UTCEPSS rescore
  15. 2026-06-23 21:31 UTCEPSS rescore
  16. 2026-06-23 08:30 UTCOSV refresh
  17. 2026-06-21 14:55 UTCEPSS rescore
  18. 2026-06-21 14:55 UTCEPSS rescore
  19. 2026-06-21 01:58 UTCEPSS rescore
  20. 2026-06-21 01:58 UTCEPSS rescore
  21. 2026-06-18 17:51 UTCEPSS rescore
  22. 2026-06-18 17:51 UTCEPSS rescore
  23. 2026-06-17 17:51 UTCEPSS rescore
  24. 2026-06-17 17:51 UTCEPSS rescore
  25. 2026-06-16 17:51 UTCEPSS rescore
Show 54 more
  1. 2026-06-15 17:46 UTCEPSS rescore
  2. 2026-06-14 23:15 UTCEPSS rescore
  3. 2026-06-14 23:15 UTCEPSS rescore
  4. 2026-06-13 22:58 UTCEPSS rescore
  5. 2026-06-13 22:58 UTCEPSS rescore
  6. 2026-06-12 23:10 UTCEPSS rescore
  7. 2026-06-12 23:10 UTCEPSS rescore
  8. 2026-06-11 13:58 UTCEPSS rescore
  9. 2026-06-11 13:58 UTCEPSS rescore
  10. 2026-06-10 22:16 UTCEPSS rescore
  11. 2026-06-10 13:20 UTCEPSS rescore
  12. 2026-06-08 14:15 UTCEPSS rescore
  13. 2026-06-08 14:15 UTCEPSS rescore
  14. 2026-06-07 15:23 UTCEPSS rescore
  15. 2026-06-07 15:23 UTCEPSS rescore
  16. 2026-06-06 13:46 UTCEPSS rescore
  17. 2026-06-06 13:46 UTCEPSS rescore
  18. 2026-06-06 08:04 UTCOSV refresh
  19. 2026-06-05 22:45 UTCEPSS rescore
  20. 2026-06-05 06:09 UTCEPSS rescore
  21. 2026-06-05 06:09 UTCEPSS rescore
  22. 2026-06-04 13:11 UTCEPSS rescore
  23. 2026-06-04 13:11 UTCEPSS rescore
  24. 2026-06-02 20:11 UTCEPSS rescore
  25. 2026-06-02 20:11 UTCEPSS rescore
  26. 2026-06-02 20:11 UTCEPSS rescore
  27. 2026-06-01 13:50 UTCEPSS rescore
  28. 2026-06-01 13:50 UTCEPSS rescore
  29. 2026-06-01 13:50 UTCEPSS rescore
  30. 2026-05-31 22:29 UTCEPSS rescore
  31. 2026-05-31 22:29 UTCEPSS rescore
  32. 2026-05-31 00:15 UTCEPSS rescore
  33. 2026-05-31 00:15 UTCEPSS rescore
  34. 2026-05-29 13:42 UTCEPSS rescore
  35. 2026-05-28 13:43 UTCEPSS rescore
  36. 2026-05-28 13:43 UTCEPSS rescore
  37. 2026-05-28 13:43 UTCEPSS rescore
  38. 2026-05-27 13:39 UTCEPSS rescore
  39. 2026-05-27 13:39 UTCEPSS rescore
  40. 2026-05-26 13:43 UTCEPSS rescore
  41. 2026-05-26 07:17 UTCEPSS rescore
  42. 2026-05-26 07:17 UTCEPSS rescore
  43. 2026-05-22 21:16 UTCEPSS rescore
  44. 2026-05-22 21:16 UTCEPSS rescore
  45. 2026-05-22 21:16 UTCEPSS rescore
  46. 2026-05-22 21:16 UTCEPSS rescore
  47. 2026-05-22 21:16 UTCEPSS rescore
  48. 2026-05-22 21:16 UTCEPSS rescore
  49. 2026-05-22 21:16 UTCEPSS rescore
  50. 2026-05-22 21:16 UTCEPSS rescore
  51. 2026-05-22 21:16 UTCEPSS rescore
  52. 2026-05-22 15:18 UTCEG score recompute
  53. 2026-05-22 15:18 UTCVendor advisory
  54. 2026-05-22 15:18 UTCGHSA enrichment

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2022-23302?
CVE-2022-23302 is a high vulnerability published on January 18, 2022. 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…
When was CVE-2022-23302 disclosed?
CVE-2022-23302 was first published in the National Vulnerability Database on January 18, 2022, with the most recent update on May 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-23302 actively exploited?
CVE-2022-23302 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.1% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-23302?
CVE-2022-23302 has a CVSS v4.0 base score of 8.8 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2022-23302?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-23302, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-23302

Explore →

Is Your Infrastructure Affected by CVE-2022-23302?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs