Apache Software Foundation · Apache Log4j
The flaw is in Apache Log4j 2.x before 2.8.2, specifically in the TCP socket server and UDP socket server components that receive serialized log events from other applications.
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.
Public exploit code (PoC-in-GitHub) appeared 4 months after disclosure. No confirmed exploitation is recorded.
No ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
2 packages in 1 ecosystem. Main package: org.apache.logging.log4j:log4j.
Upgrade to 2.8.2 or later
Set the version to 2.8.2 or later in your pom.xml or build.gradle.
The first fix for CVE-2017-5645. No other CVE tracked by Patchfirst affects this package.
| If you run | Upgrade to |
|---|---|
| 2.0 up to 2.8.2 | 2.8.2 |
“Up to” means the second version is the fix and is not affected.
Forks, repackagings and products that include the affected code. Each has its own fixed version.