CVE-2022-23305: By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the val

Q: How do I fix CVE-2022-23305?

log4j: upgrade to newer than 1.2.17; snapmanager: mitigate or apply the listed mitigation; snapmanager: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2022-23305 being exploited?

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

Q: What does CVE-2022-23305 affect?

CVE-2022-23305 affects log4j, snapmanager, snapmanager. Severity is critical (CVSS 9.8). By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows atta

Q: How urgent is CVE-2022-23305?

Priority 77/100. Critical severity; EPSS top 1%: very likely to be exploited; Public exploit reference; CISA SSVC: automatable with total technical impact; Remotely exploitable, no login, no user action; On your watchlist

This week

CRITICAL 9.8REMOTEWATCHLISTUPGRADEMITIGATEMITIGATE

CVE-2022-23305 is a critical-severity flaw (CVSS 9.8) affecting log4j, snapmanager, snapmanager. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

By design, the JDBCAppender in Log4j 1.2.x accepts an SQL statement as a configuration parameter where the values to be inserted are converters from PatternLayout. The message converter, %m, is likely to always be included. This allows attackers to manipulate the SQL by entering crafted strings into input fields or headers of an application that are logged allowing unintended SQL queries to be executed. Note this issue only affects Log4j 1.x when

Why this priority

Critical severity
EPSS top 1%: very likely to be exploited
Public exploit reference
CISA SSVC: automatable with total technical impact
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

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

Publisher (CNA): Apache Software Foundation · Vendor: apache · broadcom · netapp · 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 log4j UPGRADE

Affected: >= 1.2 and <= 1.2.17

Fixed in: newer than 1.2.17

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 newer than 1.2.17 (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.

netapp snapmanager MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

1. Check installed version

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

No fixed or unaffected release known

Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

netapp snapmanager MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

1. Check installed version

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

No fixed or unaffected release known

Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

broadcom brocade sannav MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy brocade-sannav || rpm -q brocade-sannav || brocade-sannav --version

No fixed or unaffected release known

Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

qos reload4j UPGRADE

Affected: < 1.2.18.2

Fixed in: 1.2.18.2

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.2 (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.

Exact fixes by distribution

A distro patch exists: prefer upgrading over downgrading.

Maven · log4j:log4j · NO FIX YET · vulnerable: <= 1.2.17 · source

Maven · org.zenframework.z8.dependencies.commons:log4j-1.2.17 · NO FIX YET · vulnerable: <= 2.0 · source

Fedora 46 · root · FIXED · 6.40.04-7.fc46 · FEDORA-2026-7329868400 · source

sudo dnf upgrade --advisory=FEDORA-2026-7329868400

Ubuntu 22.04 · apache-log4j1.2 · NOT AFFECTED

Ubuntu 20.04 · apache-log4j1.2 · FIXED · 1.2.17-9ubuntu0.2

sudo apt update && sudo apt install --only-upgrade apache-log4j1.2 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' apache-log4j1.2)" ge "1.2.17-9ubuntu0.2" && echo PATCHED || echo STILL-VULNERABLE

Ubuntu 24.04 · apache-log4j1.2 · NOT AFFECTED

Ubuntu 24.10 · apache-log4j1.2 · NOT AFFECTED

Ubuntu 25.04 · apache-log4j1.2 · NOT AFFECTED

Debian 12 · apache-log4j1.2 · FIXED · 1.2.17-11

sudo apt update && sudo apt install --only-upgrade apache-log4j1.2 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' apache-log4j1.2)" ge "1.2.17-11" && echo PATCHED || echo STILL-VULNERABLE

Debian 13 · apache-log4j1.2 · FIXED · 1.2.17-11

sudo apt update && sudo apt install --only-upgrade apache-log4j1.2 dpkg --compare-versions "$(dpkg-query -W -f='${Version}' apache-log4j1.2)" ge "1.2.17-11" && echo PATCHED || echo STILL-VULNERABLE

RHEL 6 Extended Lifecycle Support · log4j · FIXED · log4j-1.2.14-6.6.el6_10