CVE-2022-23307: CVE-2020-9493 identified a deserialization issue that was present in Apache Chainsaw

This week

HIGH 8.8WATCHLISTUPGRADEUPGRADEUPGRADE

CVE-2022-23307 is a high-severity flaw (CVSS 8.8) affecting chainsaw, log4j, reload4j. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

High severity
EPSS top 1%: very likely to be exploited
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	54.4% (top 1%)
CISA exploited list	No
Weakness	CWE-502
Published	2022-01-18
Last modified	2026-06-17

Publisher (CNA): Apache Software Foundation · Vendor: apache · oracle · qos

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-01-18 16:15 UTCPublished CVE record published
2026-06-17 04:29 UTCUpdated Record last modified

apache chainsaw UPGRADE

Affected: < 2.1.0

Fixed in: 2.1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy chainsaw || rpm -q chainsaw || chainsaw --version

2. UPGRADE to 2.1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade chainsaw

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade chainsaw

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

apache log4j UPGRADE

Affected: >= 1.2 and < 2.0

Fixed in: 2.0

Safe to downgrade to: a release before 1.2

1. Check installed version

apt-cache policy log4j || rpm -q log4j || log4j --version

2. UPGRADE to 2.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade log4j

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade log4j

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.2 (Debian / Ubuntu)

apt-cache madison log4j sudo apt install log4j=<VERSION_BEFORE_1.2> sudo apt-mark hold log4j

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list log4j sudo dnf downgrade log4j-<VERSION_BEFORE_1.2> sudo dnf versionlock add log4j

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

qos reload4j UPGRADE

Affected: < 1.2.18.1

Fixed in: 1.2.18.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy reload4j || rpm -q reload4j || reload4j --version

2. UPGRADE to 1.2.18.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade reload4j

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade reload4j

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

oracle advanced supply chain planning DOWNGRADE

Affected: 12.1 · 12.2

Fixed in: no fixed release known

Safe to downgrade to: a release before 12.1

1. Check installed version

apt-cache policy advanced-supply-chain-planning || rpm -q advanced-supply-chain-planning || advanced-supply-chain-planning --version

2. No fixed release: DOWNGRADE to a release before 12.1 (Debian / Ubuntu)

apt-cache madison advanced-supply-chain-planning sudo apt install advanced-supply-chain-planning=<VERSION_BEFORE_12.1> sudo apt-mark hold advanced-supply-chain-planning

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list advanced-supply-chain-planning sudo dnf downgrade advanced-supply-chain-planning-<VERSION_BEFORE_12.1> sudo dnf versionlock add advanced-supply-chain-planning

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

oracle business intelligence DOWNGRADE

Affected: 5.9.0.0.0 · 12.2.1.3.0 · 12.2.1.4.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 5.9.0.0.0

1. Check installed version

apt-cache policy business-intelligence || rpm -q business-intelligence || business-intelligence --version

2. No fixed release: DOWNGRADE to a release before 5.9.0.0.0 (Debian / Ubuntu)

apt-cache madison business-intelligence sudo apt install business-intelligence=<VERSION_BEFORE_5.9.0.0.0> sudo apt-mark hold business-intelligence

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list business-intelligence sudo dnf downgrade business-intelligence-<VERSION_BEFORE_5.9.0.0.0> sudo dnf versionlock add business-intelligence

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

oracle business process management suite DOWNGRADE

Affected: 12.2.1.3.0 · 12.2.1.4.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 12.2.1.3.0

1. Check installed version

apt-cache policy business-process-management-suite || rpm -q business-process-management-suite || business-process-management-suite --version

2. No fixed release: DOWNGRADE to a release before 12.2.1.3.0 (Debian / Ubuntu)

apt-cache madison business-process-management-suite sudo apt install business-process-management-suite=<VERSION_BEFORE_12.2.1.3.0> sudo apt-mark hold business-process-management-suite

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list business-process-management-suite sudo dnf downgrade business-process-management-suite-<VERSION_BEFORE_12.2.1.3.0> sudo dnf versionlock add business-process-management-suite

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-23307?

chainsaw: upgrade to 2.1.0; log4j: upgrade to 2.0; reload4j: upgrade to 1.2.18.1. Exact commands for each OS are on this page.

Is CVE-2022-23307 being exploited?

CVE-2022-23307 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-23307 affect?

CVE-2022-23307 affects chainsaw, log4j, reload4j. Severity is high (CVSS 8.8). 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.

How urgent is CVE-2022-23307?

Priority 61/100. High severity; EPSS top 1%: very likely to be exploited; On your watchlist

Software pages

Apache Log4j vulnerabilities

Related CVEs

CVE-2020-9493 CRITICAL 9.8 UPGRADE UPGRADE A deserialization flaw was found in Apache Chainsaw versions prior to 2.1.0 which could lead to malicious code

References

← Back to latest CVEs