CVE intelligence and bounded remediation

CVE-2022-23302 — Apache Log4J security vulnerability

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 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 Log4j 1.x when specifically configured to use JMSSink, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.

Severity
High
CVSS
8.8 (3.1)
Published
2022-01-18
CISA KEV
Not currently listed
Ecosystem
java/maven
Weaknesses
CWE-502

Affected products

  • apache / log4j
  • netapp / snapmanager
  • broadcom / brocade_sannav
  • qos / reload4j
  • oracle / advanced_supply_chain_planning / 12.1
  • oracle / advanced_supply_chain_planning / 12.2

Showing 6 representative product identities from 40 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

Unsafe deserialization and object reconstruction

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Inventory serialization formats accepted from requests, queues, caches, files, cookies, and cross-service messages.
  • Trace whether untrusted input can select classes, types, callbacks, constructors, or object hooks during decoding.
  • Identify signing, schema validation, trust-boundary, and compatibility settings for each decoder.

Remediate safely

  • Replace native object deserialization with a data-only format and explicit schema validation.
  • If replacement is not immediate, use a safe decoder with a minimal type allowlist and disable polymorphic or executable hooks.
  • Update the affected library and add inert tests for unknown types, extra fields, malformed nesting, and unsigned data.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.