CVE-2022-23302: JMSSink in all versions of Log4j 1.x is vulnerable to deserialization of untrusted data when the attacker has

This week

HIGH 8.8WATCHLISTUPGRADEMITIGATEMITIGATE

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

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

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	63.8% (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 · 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.0.1 and <= 1.2.17

Fixed in: newer than 1.2.17

Safe to downgrade to: a release before 1.0.1

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.0.1 (Debian / Ubuntu)

apt-cache madison log4j sudo apt install log4j=<VERSION_BEFORE_1.0.1> 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.0.1> 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.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.

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-23302?

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.

Is CVE-2022-23302 being exploited?

CVE-2022-23302 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-23302 affect?

CVE-2022-23302 affects log4j, snapmanager, snapmanager. Severity is high (CVSS 8.8). 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 attacke

How urgent is CVE-2022-23302?

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

Software pages

Apache Log4j vulnerabilities

Related CVEs

CVE-2026-34478 HIGH 7.5 UPGRADE Apache Log4j Core's Rfc5424Layout https://logging.apache.org/log4j/2.x/manual/layouts.html#RFC5424Layout , in
CVE-2026-34480 HIGH 7.5 UPGRADE Apache Log4j Core's XmlLayout https://logging.apache.org/log4j/2.x/manual/layouts.html#XmlLayout , in version
CVE-2026-34481 HIGH 7.5 UPGRADE Apache Log4j's JsonTemplateLayout https://logging.apache.org/log4j/2.x/manual/json-template-layout.html , in
CVE-2026-34477 MEDIUM 5.9 UPGRADE The fix for CVE-2025-68161 https://logging.apache.org/security.html#CVE-2025-68161 was incomplete: it addres
CVE-2026-34479 HIGH 7.5 UPGRADE The Log4j1XmlLayout from the Apache Log4j 1-to-Log4j 2 bridge fails to escape characters forbidden by the XML

References

← Back to latest CVEs