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.
CVE-2022-23307
“▲” beside the score: it is higher than the CVSS score beside it.
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.
Also known asEUVD-2022-0575 (ENISA EUVD) · GHSA-f7vh-qwp3-x37m (GitHub Security Advisories)Source: ENISA EUVD
- High exploitation likelihood — EPSS 54%
A fix is available — apply it.
Fixed versions, as the CVE record's CNA (Apache Software Foundation) states them in the record's workaround: "Upgrade to Apache Log4j 2 and Apache Chainsaw 2.1.0."
- CVSS v3
- 8.8
- EG Score
- 9.8CRITICALmedium confidence
- EG Risk
- 66EG Risk 66/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity98% × 45%Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation54% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 54%
- EPSS %ILE
- 99th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
- EG Likelihood
- 54% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
January 18, 2022
Last Modified
May 27, 2026
Advisory Details (2)
Auto-updated May 22, 2026Vendor 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.
- RHSA-2024:10207Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.3.11 Security update
- RHSA-2024:5856Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.1.7 on RHEL 7 security update
- RHSA-2022:5460Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 6.4.24 security update
- RHSA-2022:5459Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 6.4.24 security update
- RHSA-2022:5458Red Hat Product SecurityHigh
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 6.4.24 security update
- RHSA-2022:1299Red Hat Product SecurityLow
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.4 security update
- RHSA-2022:1297Red Hat Product SecurityLow
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.4 security update
- RHSA-2022:1296Red Hat Product SecurityLow
Red Hat Security Advisory: Red Hat JBoss Enterprise Application Platform 7.4.4 security update
- +12 more
Patch Availability(24)
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)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| log4j:log4j | 1.1.3 ... 1.2.9 (14 versions) |
| — |
| org.zenframework.z8.dependencies.commons:log4j-1.2.17 | 2.0 |
| — |
Debian:11(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j1.2 | 1.2.17-10 |
| — |
Debian:12(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j1.2 | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j1.2 | — |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j1.2 | — |
| — |
Debian:9(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| apache-log4j1.2 | 1.2.17-7, 1.2.17-7+deb9u1 |
| — |
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.
- Red HatRHSA-2022:0289IMPORTANT2022-01-18
RHSA-2022:0289 — Important
- Red HatRHSA-2022:0290IMPORTANT2022-01-18
RHSA-2022:0290 — Important
- Red HatRHSA-2022:0291IMPORTANT2022-01-18
RHSA-2022:0291 — Important
- Red HatRHSA-2022:0294IMPORTANT2022-01-18
RHSA-2022:0294 — Important
- Red HatRHSA-2022:0430IMPORTANT2022-01-18
RHSA-2022:0430 — Important
- Red HatRHSA-2022:0435IMPORTANT2022-01-18
RHSA-2022:0435 — Important
- Red HatRHSA-2022:0436IMPORTANT2022-01-18
RHSA-2022:0436 — Important
- Red HatRHSA-2022:0437IMPORTANT2022-01-18
RHSA-2022:0437 — Important
- Red HatRHSA-2022:0438IMPORTANT2022-01-18
RHSA-2022:0438 — Important
- Red HatRHSA-2022:0439IMPORTANT2022-01-18
RHSA-2022:0439 — Important
- Red HatRHSA-2022:0442IMPORTANT2022-01-18
RHSA-2022:0442 — Important
- Red HatRHSA-2022:0444IMPORTANT2022-01-18
RHSA-2022:0444 — Important
- Red HatRHSA-2022:0446IMPORTANT2022-01-18
RHSA-2022:0446 — Important
- Red HatRHSA-2022:0448IMPORTANT2022-01-18
RHSA-2022:0448 — Important
- Red HatRHSA-2022:0449IMPORTANT2022-01-18
RHSA-2022:0449 — Important
Data Freshness Timeline
(refreshed 24× in last 7d / 83× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
Showing the most recent 99 of 226 refreshes on record for this CVE.
A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 127 oldest rows on record are not shown and were not checked, so the counts can still include repeats.
- 2026-11-01 16:30 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-11-01 14:13 UTCEG score recompute
- 2026-11-01 14:13 UTCVendor advisory
- 2026-11-01 14:13 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-31 16:29 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-31 12:20 UTCEG score recompute
- 2026-10-31 12:20 UTCVendor advisory
- 2026-10-31 12:20 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-30 16:30 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-30 10:26 UTCEG score recompute
- 2026-10-30 10:26 UTCVendor advisory
- 2026-10-30 10:26 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-29 16:29 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-29 08:34 UTCEG score recompute
- 2026-10-29 08:34 UTCVendor advisory
- 2026-10-29 08:33 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-28 16:28 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-28 06:36 UTCEG score recompute
- 2026-10-28 06:36 UTCVendor advisory
- 2026-10-28 06:35 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-27 16:28 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-27 04:43 UTCEG score recompute
- 2026-10-27 04:43 UTCVendor advisory
- 2026-10-27 04:43 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-25 22:24 UTCVendor advisory
Show 74 moreShow fewer
- 2026-10-25 22:24 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-25 18:13 UTCEG score recompute
- 2026-10-25 16:29 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-24 20:31 UTCEG score recompute
- 2026-10-24 20:31 UTCVendor advisory
- 2026-10-24 20:31 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-24 16:29 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-23 18:39 UTCEG score recompute
- 2026-10-23 18:39 UTCVendor advisory
- 2026-10-23 18:38 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-22 16:45 UTCEG score recompute
- 2026-10-22 16:45 UTCVendor advisory
- 2026-10-22 16:45 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-22 16:30 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-21 16:28 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-21 14:50 UTCEG score recompute
- 2026-10-21 14:50 UTCVendor advisory
- 2026-10-21 14:50 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-20 16:29 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-20 12:57 UTCEG score recompute
- 2026-10-20 12:57 UTCVendor advisory
- 2026-10-20 12:57 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-19 16:28 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-19 11:02 UTCEG score recompute
- 2026-10-19 11:02 UTCVendor advisory
- 2026-10-19 11:02 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-18 16:28 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-18 07:55 UTCEG score recompute
- 2026-10-18 07:55 UTCVendor advisory
- 2026-10-18 07:55 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-17 06:01 UTCEG score recompute
- 2026-10-17 06:01 UTCVendor advisory
- 2026-10-17 06:01 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-16 16:34 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-16 04:07 UTCEG score recompute
- 2026-10-16 04:07 UTCVendor advisory
- 2026-10-16 04:06 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-15 16:28 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-15 01:04 UTCEG score recompute
- 2026-10-15 01:04 UTCVendor advisory
- 2026-10-15 01:04 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-14 16:29 UTCEPSS rescoreEPSS 54% · 99th percentile
- 2026-10-13 22:15 UTCEG score recompute
- 2026-10-13 22:15 UTCVendor advisory
- 2026-10-13 22:15 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-13 16:29 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-10-12 19:01 UTCVendor advisory
- 2026-10-12 19:01 UTCGHSA enrichmentGHSA-f7vh-qwp3-x37m · GitHub severity CRITICAL · GitHub CVSS 9.8
- 2026-10-12 18:59 UTCEG score recompute
- 2026-10-11 23:25 UTCEG score recompute
- 2026-10-11 13:44 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-10-10 19:56 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-10-09 20:04 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-10-08 16:40 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-10-08 08:35 UTCOSV refresh
- 2026-10-07 23:45 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-10-06 15:14 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-10-03 14:22 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-30 15:50 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-27 13:41 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-24 14:00 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-23 13:45 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-18 14:20 UTCOSV refresh
- 2026-09-17 19:23 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-16 14:05 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-15 03:06 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-12 14:57 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-11 14:49 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-11 09:33 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-08 21:57 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-06 13:45 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-05 15:25 UTCEPSS rescoreEPSS 54% · 98th percentile
- 2026-09-04 13:57 UTCEPSS rescoreEPSS 54% · 98th percentile
Related CVEs(same product + same vendor + same CWE)
Same product
6 shownDebian:9:apache-log4j1.2 · Debian:11:apache-log4j1.2 · Maven:log4j:log4j
Same vendor
10 shownredhat:RHSA-2022:0289 · redhat:RHSA-2022:0467 · redhat:RHSA-2022:0497
- CVE-2022-23305EG 9.8EPSS p99CRITICAL
- CVE-2022-23302EG 8.9EPSS p99HIGH
- CVE-2021-4104NVD 7.5EG 8.9EPSS p100HIGH
- CVE-2021-44832NVD 6.6EG 9.0EPSS p100CRITICAL
- CVE-2019-17571EG 9.8EPSS p99CRITICAL
- CVE-2021-45105NVD 5.9EG 9.0EPSS p100CRITICAL
- CVE-2021-45046EG 9.0 KEVEPSS p100CRITICAL
- CVE-2020-13935NVD 7.5EG 9.0EPSS p100CRITICAL
- CVE-2021-3859EG 7.5HIGH
- CVE-2020-14384EG 7.5HIGH
Same CWE
10 shownCWE-502
- CVE-2022-23302EG 8.9EPSS p99HIGH
- CVE-2021-45394EG 8.8HIGH
- CVE-2022-21341EG 5.3EPSS p90MEDIUM
- CVE-2021-41766EG 8.1HIGH
- CVE-2021-43297EG 9.8EPSS p97CRITICAL
- CVE-2021-42392EG 9.8EPSS p100CRITICAL
- CVE-2021-45899EG 9.8CRITICAL
- CVE-2022-21663EG 6.6EPSS p90MEDIUM
- CVE-2021-42631EG 8.1EPSS p93HIGH
- CVE-2021-43859EG 7.5EPSS p95HIGH
Frequently asked(5)
What is CVE-2022-23307?
When was the CVE record for CVE-2022-23307 published?
Is CVE-2022-23307 actively exploited?
What is the CVSS score of CVE-2022-23307?
How do I remediate CVE-2022-23307?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-23307
Is Your Infrastructure Affected by CVE-2022-23307?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.