Apache Log4j 1.x (EOL) allows DoS in Chainsaw and SocketAppender
Apache Software Foundation Apache Log4j
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.logging.log4j:log4j-core Maven |
|
|
| log4j:log4j Maven |
|
|
Apache Software Foundation Apache Log4j
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.logging.log4j:log4j-core Maven |
|
|
| log4j:log4j Maven |
|
|
** UNSUPPORTED WHEN ASSIGNED **
When using the Chainsaw or SocketAppender components with Log4j 1.x on JRE less than 1.7, an attacker that manages to cause a logging entry involving a specially-crafted (ie, deeply nested) hashmap or hashtable (depending on which logging component is in use) to be processed could exhaust the available memory in the virtual machine and achieve Denial of Service when the object is deserialized.
This issue affects Apache Log4j before 2. Affected users are recommended to update to Log4j 2.x.
NOTE: This vulnerability only affects products that are no longer supported by the maintainer.
From the CVE record · apache
Log4j 1.x is vulnerable when Chainsaw or SocketAppender runs on a JRE older than 1.7. An attacker who can cause a log entry containing a specially crafted, deeply nested hashmap or hashtable to be processed can exhaust virtual-machine memory during deserialization, causing denial of service.
Check deployments using Maven packages org.apache.logging.log4j:log4j-core or log4j:log4j at versions 1.0.4 or later but earlier than 2.0, especially those using Chainsaw or SocketAppender on a JRE older than 1.7.