Those using java.sql.Statement or java.sql.PreparedStatement in hsqldb (HyperSQL DataBase) to process untrusted input may be vulnerable to a remote code execution attack. By default it is allowed to call any static method of any Java class in the classpath resulting in code execution. The issue can be prevented by updating to 2.7.1 or by setting the system property "hsqldb.method_class_names" to classes which are allowed to be called. For example, System.setProperty("hsqldb.method_class_names", "abc") or Java argument -Dhsqldb.method_class_names="abc" can be used. From version 2.7.1 all classes by default are not accessible except those in java.lang.Math and need to be manually enabled.
The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.
| Link | Tags |
|---|---|
| https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=50212#c7 | third party advisory mailing list |
| http://hsqldb.org/doc/2.0/guide/sqlroutines-chapt.html#src_jrt_access_control | third party advisory |
| https://lists.debian.org/debian-lts-announce/2022/12/msg00020.html | third party advisory mailing list |
| https://www.debian.org/security/2023/dsa-5313 | third party advisory vendor advisory |