CVE-2021-4104: JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data

CVE-2021-4104 · Severity: low · CVSS 3.1 · Published 2021-12-14

JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data

Technologies: log4j:log4j (Maven), org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven). Vendors: Maven.

Quick answers

Is CVE-2021-4104 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2021-4104 being exploited in the wild.
How severe is CVE-2021-4104?
Low severity, with a CVSS score of 3.1, published 14 December 2021.
Which products and versions are affected?
log4j:log4j (Maven) ECOSYSTEM:introduced=1.2.0,last_affected=1.2.17; org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven) ECOSYSTEM:introduced=0,last_affected=2.0.
Is there a fix for CVE-2021-4104?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
Am I affected by CVE-2021-4104?
Check whether you run log4j:log4j (Maven) or org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Affected products

  • log4j:log4j (Maven) ECOSYSTEM:introduced=1.2.0,last_affected=1.2.17
  • org.zenframework.z8.dependencies.commons:log4j-1.2.17 (Maven) ECOSYSTEM:introduced=0,last_affected=2.0

Identifiers

  • CVE-2021-4104
  • GHSA-fp5r-v3w9-4333

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.