Schema parsing in the Java SDK of Apache Avro 1.11.3 and previous versions allows bad actors to execute arbitrary code. Users are recommended to upgrade to version 1.11.4 or 1.12.0, which fix this issue.
The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Red Hat build of Apache Camel 4.4.3 for Spring Boot | RedHat | org.apache.avro/avro | * |
Red Hat build of Apache Camel for Quarkus | RedHat | org.apache.avro/avro | * |
Red Hat build of Apicurio Registry 2.6.5 GA | RedHat | org.apache.avro/avro | * |
Red Hat JBoss Enterprise Application Platform 7 | RedHat | org.apache.avro/avro | * |
Red Hat JBoss Enterprise Application Platform 7 | RedHat | * | |
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8 | RedHat | eap7-avro-0:1.11.4-1.redhat_00001.1.el8eap | * |
Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 9 | RedHat | eap7-avro-0:1.11.4-1.redhat_00001.1.el9eap | * |
Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7 | RedHat | eap7-avro-0:1.11.4-1.redhat_00001.1.el7eap | * |
RHINT Camel-K 1.10.8 | RedHat | org.apache.avro/avro | * |
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.