CVE-2022-23302 · cross-distro fix matrix

CVE-2022-23302: 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 configurat

Affects 3 Linux releases across 3 (distro × package) combinations.

Fix per ecosystem

Each block below is a distro release where CVE-2022-23302 has a known fix. Run the listed command on that distro to remediate.

Debian bullseye

Source: Debian Security Tracker

apache-log4j1.2→ fixed in1.2.17-10+deb11u1urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y apache-log4j1.2
```

Debian bookworm

Source: Debian Security Tracker

apache-log4j1.2→ fixed in1.2.17-11urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y apache-log4j1.2
```

Debian trixie

Source: Debian Security Tracker

apache-log4j1.2→ fixed in1.2.17-11urgency: not yet assigned
```
sudo apt-get install --only-upgrade -y apache-log4j1.2
```

Are YOU affected by CVE-2022-23302?

5-second check on your actual server. Reads /etc/os-release, uname -r, and the distro's package manager; matches against this same cross-source index live.

curl https://mindsparkstack.com/scan.sh | bash

Form-based quickscan View on NVD

Continuous monitoring beats manual checking

CVE-2022-23302dropped silently in your distro's update channel. Every new CVE is the same story. StackPatch runs the matcher hourly against all 5 sources and emails the exact remediation when something new applies to one of your servers. $99 lifetime, 50 founder seats, 30-day refund.

See StackPatch ($99 lifetime)