The org.h2.util.JdbcUtils.getConnection method of the H2 database takes as parameters the class name of the driver and URL of the database. An attacker may pass a JNDI driver name and a URL leading to a LDAP or RMI servers, causing remote code execution. This can be exploited through various attack vectors, most notably through the H2 Console which leads to unauthenticated remote code execution.
The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| H2 | H2database | 1.1.000 (including) | 2.0.204 (including) |
| Red Hat JBoss Enterprise Application Platform 7 | RedHat | h2 | * |
| Red Hat JBoss Enterprise Application Platform 7.4 for RHEL 8 | RedHat | eap7-h2database-0:1.4.197-2.redhat_00004.1.el8eap | * |
| Red Hat JBoss Enterprise Application Platform 7.4 on RHEL 7 | RedHat | eap7-h2database-0:1.4.197-2.redhat_00004.1.el7eap | * |
| Red Hat Single Sign-On 7 | RedHat | h2 | * |
| Red Hat Single Sign-On 7.5 for RHEL 7 | RedHat | rh-sso7-keycloak-0:15.0.8-1.redhat_00001.1.el7sso | * |
| Red Hat Single Sign-On 7.5 for RHEL 8 | RedHat | rh-sso7-keycloak-0:15.0.8-1.redhat_00001.1.el8sso | * |
| Red Hat Single Sign-On 7.6.1 | RedHat | h2 | * |
| Red Hat Single Sign-On 7.6 for RHEL 7 | RedHat | rh-sso7-keycloak-0:18.0.3-1.redhat_00001.1.el7sso | * |
| Red Hat Single Sign-On 7.6 for RHEL 8 | RedHat | rh-sso7-keycloak-0:18.0.3-1.redhat_00001.1.el8sso | * |
| Red Hat Single Sign-On 7.6 for RHEL 9 | RedHat | rh-sso7-0:1-5.el9sso | * |
| Red Hat Single Sign-On 7.6 for RHEL 9 | RedHat | rh-sso7-javapackages-tools-0:6.0.0-7.el9sso | * |
| Red Hat Single Sign-On 7.6 for RHEL 9 | RedHat | rh-sso7-keycloak-0:18.0.3-1.redhat_00001.1.el9sso | * |
| RHINT Camel-Q 2.2.1 | RedHat | h2 | * |
| H2database | Ubuntu | bionic | * |
| H2database | Ubuntu | esm-apps/bionic | * |
| H2database | Ubuntu | esm-apps/xenial | * |
| H2database | Ubuntu | focal | * |
| H2database | Ubuntu | hirsute | * |
| H2database | Ubuntu | impish | * |
| H2database | Ubuntu | jammy | * |
| H2database | Ubuntu | kinetic | * |
| H2database | Ubuntu | lunar | * |
| H2database | Ubuntu | trusty | * |
| H2database | 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.