CVE-2019-17571GHSA-2QRG-X229-3V8Q
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely exe
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 3 proofs of concept on GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
Included in Log4j 1.2 is a SocketServer class that is vulnerable to deserialization of untrusted data which can be exploited to remotely execute arbitrary code when combined with a deserialization gadget when listening to untrusted network traffic for log data. This affects Log4j versions up to 1.2 up to 1.2.17.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Apache Software Foundation Log4j
versions up to 1.2.17
- log4j:log4jMaven
From 1.2 · through 1.2.17
- org.zenframework.z8.dependencies.commons:log4j-1.2.17Maven
2.0
References 28
lists.apache.org
- thread.html/8ab32b4c9f1826f20add7c40be08909de9f58a89dc1de9c09953f5ac@<issues.activemq.apache.org>
- thread.html/44491fb9cc19acc901f7cff34acb7376619f15638439416e3e14761c@<dev.tika.apache.org>
- thread.html/277b4b5c2b0e06a825ccec565fa65bd671f35a4d58e3e2ec5d0618e1@<dev.tika.apache.org>
- thread.html/479471e6debd608c837b9815b76eab24676657d4444fcfd5ef96d6e6@<dev.tika.apache.org>
- thread.html/6114ce566200d76e3cc45c521a62c2c5a4eac15738248f58a99f622c@<issues.activemq.apache.org>
- thread.html/564f03b4e9511fcba29c68fc0299372dadbdb002718fa8edcc4325e4@<jira.kafka.apache.org>
- thread.html/r2756fd570b6709d55a61831ca028405bcb3e312175a60bc5d911c81f@<jira.kafka.apache.org>
- thread.html/752ec92cd1e334a639e79bfbd689a4ec2c6579ec5bb41b53ffdf358d@<dev.kafka.apache.org>
- thread.html/r189aaeaad897f7d6b96f7c43a8ef2dfb9f6e9f8c1cc9ad182ce9b9ae@<jira.kafka.apache.org>
- thread.html/r3c575cabc7386e646fb12cb82b0b38ae5a6ade8a800f827107824495@<jira.kafka.apache.org>
- thread.html/rf2567488cfc9212b42e34c6393cfa1c14e30e4838b98dda84d71041f@<dev.tika.apache.org>
- thread.html/r8a1cfd4705258c106e488091fcec85f194c82f2bbde6bd151e201870@<jira.kafka.apache.org>
- thread.html/r944183c871594fe9a555b8519a7c945bbcf6714d72461aa6c929028f@<issues.zookeeper.apache.org>
- thread.html/rbdf18e39428b5c80fc35113470198b1fe53b287a76a46b0f8780b5fd@<dev.zookeeper.apache.org>
- thread.html/r05755112a8c164abc1004bb44f198b1e3d8ca3d546a8f13ebd3aa05f@<issues.zookeeper.apache.org>
- thread.html/r3a85514a518f3080ab1fc2652cfe122c2ccf67cfb32356acb1b08fe8@<dev.tika.apache.org>
- thread.html/r356d57d6225f91fdc30f8b0a2bed229d1ece55e16e552878c5fa809a@<issues.zookeeper.apache.org>
- thread.html/rf1b434e11834a4449cd7addb69ed0aef0923112b5938182b363a968c@<notifications.zookeeper.apache.org>
- thread.html/rc628307962ae1b8cc2d21b8e4b7dd6d7755b2dd52fa56a151a27e4fd@<issues.zookeeper.apache.org>
- thread.html/r6aec6b8f70167fa325fb98b3b5c9ce0ffaed026e697b69b85ac24628@<issues.zookeeper.apache.org>
- thread.html/rc1eaed7f7d774d5d02f66e49baced31e04827a1293d61a70bd003ca7@<dev.tika.apache.org>
- thread.html/r681b4432d0605f327b68b9f8a42662993e699d04614de4851c35ffd1@<dev.tika.apache.org>
- thread.html/ra38785cfc0e7f17f8e24bebf775dd032c033fadcaea29e5bc9fffc60@<dev.tika.apache.org>
- thread.html/r746fbc3fc13aee292ae6851f7a5080f592fa3a67b983c6887cdb1fc5@<dev.tika.apache.org>
- thread.html/rdec0d8ac1f03e6905b0de2df1d5fcdb98b94556e4f6cccf7519fdb26@<dev.tika.apache.org>