JDBC LogFactory 任意类加载/构造导致潜在 RCE
openGauss-server openGauss-connector-jdbc
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| openGauss-server openGauss-connector-jdbc openEuler, Centos |
|
|
openGauss-server openGauss-connector-jdbc
| Product | Affected | Fixed in |
|---|---|---|
| openGauss-server openGauss-connector-jdbc openEuler, Centos |
|
|
在 openGauss-connector-jdbc 的 pgjdbc/src/main/java/org/postgresql/log/LogFactory.java 中,LogFactory 根据 JDBC 连接参数中的 logger 类名调用 Class.forName 加载类后,直接反射调用以 String 为参数的构造函数,再转换为 Log。缺少 asSubclass(Log.class) 校验,非 Log 实现类也会在类型检查前被实例化。因此,当攻击者可控制 JDBC URL 或连接属性中的 logger 类名,且客户端 classpath 中存在可被加载的类时,可能在客户端触发非预期的类加载与构造副作用。
此漏洞自 JDBC 1.1.0引入,影响 1.1.0 及之后的 2.x、3.x、5.x、6.x 各版本及补丁(含 6.0.0 分支最新 6.0.6),以及 7.0.0-RC1、7.0.0-RC2、7.0.0-RC3,并在 7.0.0-LTS 版本修复。修复在 Class.forName 之后先执行 asSubclass(Log.class),仅允许 Log 子类进入构造。修复pr见https://gitcode.com/opengauss/openGauss-connector-jdbc/pull/423。
From the CVE record · openGauss
LogFactory loads the logger class named in JDBC connection settings and invokes its String constructor before checking whether it implements Log. If an attacker can control the logger class name in a JDBC URL or connection properties, and a loadable class exists on the client classpath, they may trigger unintended class loading and constructor side effects on the client.
Teams using openGauss-connector-jdbc should check versions from 1.1.0 onward in the 2.x, 3.x, 5.x and 6.x lines (including 6.0.6), as well as 7.0.0-RC1 through 7.0.0-RC3.