CVE-2022-23307

CRITICALPre-NVD 8.89.8▲
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-01-19. The CNA's CVSS baseline 8.8; sources differ by 1.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cna:apache, epss, ghsa
Elevated
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 54%
CISA-KEV: Not listedEPSS PROB: 54%CVSS: 8.8Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.

CVSS v3
8.8
EG Score
9.8CRITICALmedium confidence
EG Risk
66
EG Risk 66/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation54% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
54%
EPSS %ILE
98th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

January 18, 2022

Last Modified

May 27, 2026

Advisory Details (2)

Auto-updated May 22, 2026
Patch available.
generic

Apache log4j 1.2 -

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

Vendor Advisories for CVE-2022-23307(20)

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

Patch Availability(23)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhateap7-xml-security-0:2.2.3-2.redhat_00001.1.el7eap2024-11-25redhat
redhateap7-log4j-jboss-logmanager-0:1.2.2-1.Final_redhat_00002.1.ep7.el72024-08-26redhat
redhatjbossweb-0:7.5.32-2.Final_redhat_1.2.ep6.el62022-06-30redhat
redhatpatch2022-06-30redhat
redhatjbossweb-0:7.5.32-2.Final_redhat_1.2.ep6.el72022-06-30redhat
redhateap7-log4j-0:2.17.1-1.redhat_00001.1.el7eap2022-04-11redhat
redhatlog4j2022-04-11redhat
redhateap7-log4j-0:2.17.1-1.redhat_00001.1.el8eap2022-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-sso7-keycloak-0:15.0.4-1.redhat_00003.1.el8sso2022-02-07redhat
redhatlog4j-0:1.2.17-18.el7_42022-02-07redhat
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
redhatrh-sso-7/sso74-openshift-rhel8:7.4-452022-02-07redhat
redhatrh-maven36-log4j12-0:1.2.17-23.4.el72022-02-03redhat
redhateap7-log4j-jboss-logmanager-0:1.2.2-1.Final_redhat_00002.1.el7eap2022-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

(7 across 6 ecosystems)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
log4j:log4j1.1.3 ... 1.2.9 (14 versions)
  • every version through 1.2.17: no fix on record
—
org.zenframework.z8.dependencies.commons:log4j-1.2.172.0
  • every version through 2.0: no fix on record
—
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j1.21.2.17-10
  • every version up to 1.2.17-10+deb11u1: fixed in 1.2.17-10+deb11u1
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j1.2—
  • every version up to 1.2.17-11: fixed in 1.2.17-11
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j1.2—
  • every version up to 1.2.17-11: fixed in 1.2.17-11
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j1.2—
  • every version up to 1.2.17-11: fixed in 1.2.17-11
—
Debian:9(1)
PackageVulnerable rangeFix by version rangeDependents
apache-log4j1.21.2.17-7, 1.2.17-7+deb9u1
  • every version up to 1.2.17-7+deb9u2: fixed in 1.2.17-7+deb9u2
—

Weakness Classification(1)

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

Additional Vendor Advisories

(15)

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 7× in last 7d / 19× 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.

Showing the most recent 100 of 150 total refreshes for this CVE.

  1. 2026-10-09 20:04 UTCEPSS rescore
  2. 2026-10-08 16:40 UTCEPSS rescore
  3. 2026-10-08 08:35 UTCOSV refresh
  4. 2026-10-07 23:45 UTCEPSS rescore
  5. 2026-10-06 15:14 UTCEPSS rescore
  6. 2026-10-03 14:23 UTCEPSS rescore
  7. 2026-10-03 14:22 UTCEPSS rescore
  8. 2026-09-30 15:50 UTCEG score recompute
  9. 2026-09-30 15:00 UTCEPSS rescore
  10. 2026-09-27 13:41 UTCEPSS rescore
  11. 2026-09-24 14:00 UTCEPSS rescore
  12. 2026-09-23 13:45 UTCEPSS rescore
  13. 2026-09-18 14:20 UTCOSV refresh
  14. 2026-09-17 19:23 UTCEPSS rescore
  15. 2026-09-16 14:05 UTCEPSS rescore
  16. 2026-09-15 03:06 UTCEPSS rescore
  17. 2026-09-12 14:57 UTCEPSS rescore
  18. 2026-09-11 14:49 UTCEPSS rescore
  19. 2026-09-11 09:33 UTCEPSS rescore
  20. 2026-09-08 21:57 UTCEPSS rescore
  21. 2026-09-06 13:45 UTCEPSS rescore
  22. 2026-09-05 15:25 UTCEPSS rescore
  23. 2026-09-04 13:57 UTCEPSS rescore
  24. 2026-09-01 13:51 UTCEPSS rescore
  25. 2026-08-30 19:14 UTCEPSS rescore
Show 75 more
  1. 2026-08-30 16:51 UTCOSV refresh
  2. 2026-08-30 01:19 UTCEPSS rescore
  3. 2026-08-28 21:38 UTCEPSS rescore
  4. 2026-08-26 14:43 UTCEPSS rescore
  5. 2026-08-24 14:13 UTCEPSS rescore
  6. 2026-08-21 23:46 UTCEPSS rescore
  7. 2026-08-20 22:52 UTCEPSS rescore
  8. 2026-08-19 17:01 UTCEPSS rescore
  9. 2026-08-18 13:45 UTCEPSS rescore
  10. 2026-08-17 13:44 UTCEPSS rescore
  11. 2026-08-16 14:53 UTCEPSS rescore
  12. 2026-08-16 02:11 UTCEPSS rescore
  13. 2026-08-15 01:27 UTCEPSS rescore
  14. 2026-08-14 04:49 UTCOSV refresh
  15. 2026-08-13 21:57 UTCEPSS rescore
  16. 2026-08-12 13:48 UTCEPSS rescore
  17. 2026-08-07 16:24 UTCEPSS rescore
  18. 2026-08-06 13:44 UTCEPSS rescore
  19. 2026-08-05 19:15 UTCEPSS rescore
  20. 2026-08-02 02:24 UTCEPSS rescore
  21. 2026-07-30 16:25 UTCEPSS rescore
  22. 2026-07-30 01:28 UTCEPSS rescore
  23. 2026-07-29 09:37 UTCOSV refresh
  24. 2026-07-28 15:33 UTCEPSS rescore
  25. 2026-07-26 14:52 UTCEPSS rescore
  26. 2026-07-26 14:52 UTCEPSS rescore
  27. 2026-07-25 14:15 UTCEPSS rescore
  28. 2026-07-24 14:15 UTCEPSS rescore
  29. 2026-07-23 14:16 UTCEPSS rescore
  30. 2026-07-23 02:08 UTCEG score recompute
  31. 2026-07-22 22:55 UTCEG score recompute
  32. 2026-07-22 14:06 UTCEPSS rescore
  33. 2026-07-22 14:06 UTCEPSS rescore
  34. 2026-07-21 15:22 UTCEPSS rescore
  35. 2026-07-21 15:22 UTCEPSS rescore
  36. 2026-07-20 17:05 UTCEPSS rescore
  37. 2026-07-19 02:27 UTCEPSS rescore
  38. 2026-07-16 17:00 UTCEPSS rescore
  39. 2026-07-16 17:00 UTCEPSS rescore
  40. 2026-07-15 16:56 UTCEPSS rescore
  41. 2026-07-15 16:56 UTCEPSS rescore
  42. 2026-07-13 22:27 UTCEPSS rescore
  43. 2026-07-13 06:11 UTCEPSS rescore
  44. 2026-07-13 06:11 UTCEPSS rescore
  45. 2026-07-12 05:44 UTCEPSS rescore
  46. 2026-07-12 02:11 UTCOSV refresh
  47. 2026-07-11 08:25 UTCEPSS rescore
  48. 2026-07-09 19:07 UTCEPSS rescore
  49. 2026-07-08 15:12 UTCEPSS rescore
  50. 2026-07-06 16:25 UTCEPSS rescore
  51. 2026-07-06 16:25 UTCEPSS rescore
  52. 2026-07-04 06:29 UTCEPSS rescore
  53. 2026-07-04 06:29 UTCEPSS rescore
  54. 2026-07-01 15:04 UTCEPSS rescore
  55. 2026-06-30 23:20 UTCEPSS rescore
  56. 2026-06-30 23:20 UTCEPSS rescore
  57. 2026-06-28 04:54 UTCEPSS rescore
  58. 2026-06-28 04:54 UTCEPSS rescore
  59. 2026-06-27 03:07 UTCEPSS rescore
  60. 2026-06-25 13:48 UTCEPSS rescore
  61. 2026-06-24 14:03 UTCEPSS rescore
  62. 2026-06-24 14:03 UTCEPSS rescore
  63. 2026-06-23 21:31 UTCEPSS rescore
  64. 2026-06-23 21:31 UTCEPSS rescore
  65. 2026-06-23 08:30 UTCOSV refresh
  66. 2026-06-21 14:55 UTCEPSS rescore
  67. 2026-06-21 14:55 UTCEPSS rescore
  68. 2026-06-21 01:58 UTCEPSS rescore
  69. 2026-06-21 01:58 UTCEPSS rescore
  70. 2026-06-18 17:51 UTCEPSS rescore
  71. 2026-06-18 17:51 UTCEPSS rescore
  72. 2026-06-17 17:51 UTCEPSS rescore
  73. 2026-06-17 17:51 UTCEPSS rescore
  74. 2026-06-16 17:51 UTCEPSS rescore
  75. 2026-06-15 17:46 UTCEPSS rescore

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

Frequently asked(5)

What is CVE-2022-23307?
CVE-2022-23307 is a critical vulnerability published on January 18, 2022. CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw. Prior to Chainsaw V2.0 Chainsaw was a component of Apache Log4j 1.2.x where the same issue exists.
When was CVE-2022-23307 disclosed?
CVE-2022-23307 was first published 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-23307 actively exploited?
CVE-2022-23307 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 54% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2022-23307?
CVE-2022-23307 has a CVSS base score of 8.8 (the CNA's own assessment, by apache; NVD's own analysis pending). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.8 (CRITICAL).
How do I remediate CVE-2022-23307?
A fix for CVE-2022-23307 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2022-23307 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2022-23307?

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

Book a Demo →Browse All CVEs