Skip to content

← Public intelligence

Maven package

org.apache.logging.log4j:log4j

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Low, CVSS 3.7MavenPublished

    Improper validation of certificate with host mismatch in Apache Log4j SMTP appender

    CVE-2020-9488 · GHSA-vwqq-5vrc-xw9h

    Affected
    • Maven org.apache.logging.log4j:log4j >= 2.13.0, < 2.13.2; >= 2.4.0, < 2.12.3; < 2.3.2
    Fixed in
    2.12.32.13.22.3.2· Vendor fix available
    Issue
    Improper validation of certificate with host mismatch in Apache Log4j SMTP appender prior to version 2.13.2. This could allow an SMTPS connection to be intercepted by a man-in-the-middle attack which could leak any log messages sent through that appender.

    Recommended action: Upgrade to 2.13.2, 2.12.3 or 2.3.2 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. Critical, CVSS 9.8MavenPublished

    Deserialization of Untrusted Data in Log4j

    CVE-2017-5645 · GHSA-fxph-q3j8-mv87

    Affected
    • Maven org.apache.logging.log4j:log4j >= 2.0, < 2.8.2
    Fixed in
    2.8.2· Vendor fix available
    Issue
    In Apache Log4j 2.x before 2.8.2, when using the TCP socket server or UDP socket server to receive serialized log events from another application, a specially crafted binary payload can be sent that, when deserialized, can execute arbitrary code.

    Recommended action: Upgrade to 2.8.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →