Maven (Java)Worst: Critical2 advisories

org.apache.logging.log4j:log4j: known vulnerabilities

org.apache.logging.log4j:log4j has 2 reviewed security advisories in the GitHub Advisory Database — 1 critical, 1 low. The most recent was published 2020-04-27. Each one below lists the affected version range, the release that fixes it, its CVE and severity. SkyShield matches these against the org.apache.logging.log4j:log4j versions running across your servers, containers and images, and ranks what to patch first.

How to fix org.apache.logging.log4j:log4j

Upgrade org.apache.logging.log4j:log4j to a release at or above the fixed version shown for each advisory below. For Maven (Java):

Bump the dependency to 2.3.2 in your pom.xml or build.gradle

SkyShield checks the installed version on every machine and container, so you can see which hosts are still on an affected release after you roll the fix out.

Advisories (2)

Improper validation of certificate with host mismatch in Apache Log4j SMTP appender Low 3.7 CWE-295 — Affected: before 2.3.2. Fixed in 2.3.2. Published 2020-04-27. GHSA-vwqq-5vrc-xw9h · CVE-2020-9488
Deserialization of Untrusted Data in Log4j Critical 9.8 CWE-502 — Affected: from 2.0 up to 2.8.2. Fixed in 2.8.2. Published 2017-04-17. GHSA-fxph-q3j8-mv87 · CVE-2017-5645

Find org.apache.logging.log4j:log4j across your fleet

Install one agent per server and connect your cloud. SkyShield matches your packages and images against GHSA, CISA KEV and EPSS and shows the fix per machine. Free for one server, then from $49 per server a month. Start free.