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.
The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Log4j | Apache | * | 1.2.17 (including) |
| Red Hat Enterprise Linux 6 Extended Lifecycle Support | RedHat | log4j-0:1.2.14-6.7.el6_10 | * |
| Red Hat Enterprise Linux 7 | RedHat | log4j-0:1.2.17-16.el7_4 | * |
| Red Hat Fuse 7.3.1 | RedHat | * | |
| Red Hat JBoss BPMS 6.4 | RedHat | * | |
| Red Hat JBoss BRMS 6.4 | RedHat | * | |
| Red Hat JBoss Data Grid 7.1 | RedHat | * | |
| Red Hat JBoss Data Virtualization 6.4.8.SP1 | RedHat | * | |
| Red Hat JBoss Data Virtualization 6.4.8.SP2 | RedHat | * | |
| Red Hat JBoss EAP 7 | RedHat | * | |
| Red Hat JBoss Enterprise Application Platform 5.2 security update | RedHat | * | |
| Red Hat JBoss Enterprise Application Platform 5 for RHEL 5 | RedHat | log4j-0:1.2.14-19.patch_01.ep5.el5 | * |
| Red Hat JBoss Enterprise Application Platform 5 for RHEL 6 | RedHat | log4j-0:1.2.14-19.patch_01.ep5.el6 | * |
| Red Hat JBoss Enterprise Application Platform 6.4 | RedHat | * | |
| Red Hat JBoss Enterprise Application Platform 6.4 for RHEL 6 | RedHat | jboss-ec2-eap-0:7.5.17-1.Final_redhat_4.ep6.el6 | * |
| Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 6 | RedHat | eap7-jboss-ec2-eap-0:7.0.8-1.GA_redhat_1.ep7.el6 | * |
| Red Hat JBoss Enterprise Application Platform 7.0 for RHEL 7 | RedHat | eap7-jboss-ec2-eap-0:7.0.8-1.GA_redhat_1.ep7.el7 | * |
| Red Hat JBoss Web Server 3.1 | RedHat | * | |
| Red Hat JBoss Web Server 3 for RHEL 6 | RedHat | log4j-eap6-0:1.2.16-12.redhat_3.1.ep6.el6 | * |
| Red Hat JBoss Web Server 3 for RHEL 6 | RedHat | tomcat7-0:7.0.70-22.ep7.el6 | * |
| Red Hat JBoss Web Server 3 for RHEL 6 | RedHat | tomcat8-0:8.0.36-24.ep7.el6 | * |
| Red Hat JBoss Web Server 3 for RHEL 6 | RedHat | tomcat-native-0:1.2.8-10.redhat_10.ep7.el6 | * |
| Red Hat JBoss Web Server 3 for RHEL 7 | RedHat | log4j-eap6-0:1.2.16-12.redhat_3.1.ep6.el7 | * |
| Red Hat JBoss Web Server 3 for RHEL 7 | RedHat | tomcat7-0:7.0.70-22.ep7.el7 | * |
| Red Hat JBoss Web Server 3 for RHEL 7 | RedHat | tomcat8-0:8.0.36-24.ep7.el7 | * |
| Red Hat JBoss Web Server 3 for RHEL 7 | RedHat | tomcat-native-0:1.2.8-10.redhat_10.ep7.el7 | * |
| Apache-log4j1.2 | Ubuntu | bionic | * |
| Apache-log4j1.2 | Ubuntu | disco | * |
| Apache-log4j1.2 | Ubuntu | eoan | * |
| Apache-log4j1.2 | Ubuntu | esm-apps/xenial | * |
| Apache-log4j1.2 | Ubuntu | esm-infra-legacy/trusty | * |
| Apache-log4j1.2 | Ubuntu | trusty | * |
| Apache-log4j1.2 | Ubuntu | trusty/esm | * |
| Apache-log4j1.2 | Ubuntu | xenial | * |
It is often convenient to serialize objects for communication or to save them for later use. However, deserialized data or code can often be modified without using the provided accessor functions if it does not use cryptography to protect itself. Furthermore, any cryptography would still be client-side security – which is a dangerous security assumption. Data that is untrusted can not be trusted to be well-formed. When developers place no restrictions on “gadget chains,” or series of instances and method invocations that can self-execute during the deserialization process (i.e., before the object is returned to the caller), it is sometimes possible for attackers to leverage them to perform unauthorized actions, like generating a shell.