Deserialization of Untrusted Data in Log4j
Apache Software Foundation Apache Log4j
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.logging.log4j:log4j Maven |
|
|
| org.apache.logging.log4j:log4j-core Maven |
|
|
Apache Software Foundation Apache Log4j
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.logging.log4j:log4j Maven |
|
|
| org.apache.logging.log4j:log4j-core Maven |
|
|
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.
From the CVE record · apache
Apache Log4j 2.x before 2.8.2 is vulnerable when its TCP or UDP socket server receives serialized log events from another application. An attacker who can send a specially crafted binary payload to the server can cause arbitrary code execution when the payload is deserialized.
Engineers running Maven packages org.apache.logging.log4j:log4j or org.apache.logging.log4j:log4j-core at versions 2.0 or later but earlier than 2.8.2 should check their deployments.