CriticalGHSA-fxph-q3j8-mv87CVE-2017-5645

Deserialization of Untrusted Data in Log4j

Published 6 Jan 2020 · Updated 14 Mar 2024

Is your project on an affected org.apache.logging.log4j:log4j?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected packages

Affected
>=2.0 <2.8.2
Fixed in
2.8.2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j -DdepVersion=2.8.2 -DforceVersion=true
Affected
>=2.0 <2.8.2
Fixed in
2.8.2
Update to the fixed version for your release line, for example:mvn versions:use-dep-version -Dincludes=org.apache.logging.log4j:log4j-core -DdepVersion=2.8.2 -DforceVersion=true

Details

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.

Is GHSA-fxph-q3j8-mv87 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected org.apache.logging.log4j:log4j, and gives you the command that fixes it.

More advisories for org.apache.logging.log4j:log4j

  • LowCVE-2020-9488Improper validation of certificate with host mismatch in Apache Log4j SMTP appender · 5 Jun 2020
org.apache.logging.log4j:log4j security overview

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.