first commit
Some checks failed
Vulhub Format Check and Lint / format-check (push) Has been cancelled
Vulhub Format Check and Lint / markdown-check (push) Has been cancelled
Vulhub Docker Image CI / longtime-images-test (push) Has been cancelled
Vulhub Docker Image CI / images-test (push) Has been cancelled

This commit is contained in:
2025-09-06 16:08:15 +08:00
commit 63285f61aa
2624 changed files with 88491 additions and 0 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 59 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 22 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

View File

@@ -0,0 +1,55 @@
# H2 Database Web Console Pre-Auth JNDI Injection RCE (CVE-2021-42392)
[中文版本(Chinese version)](README.zh-cn.md)
H2 database is a fast, open-source Java-based relational database management system (RDBMS) that can be used in both embedded (within a Java application) and client-server modes.
Springboot with h2 database comes with a web management page if you set the following options:
```
spring.h2.console.enabled=true
spring.h2.console.settings.web-allow-others=true
```
H2 Database version before 1.4.206 with this management page supports to use JNDI to load the JDBC driver, which can lead to remote code execution via JNDI injection.
References:
- <https://jfrog.com/blog/the-jndi-strikes-back-unauthenticated-rce-in-h2-database-console/>
- <https://mp.weixin.qq.com/s?__biz=MzI2NTM1MjQ3OA==&mid=2247483658&idx=1&sn=584710da0fbe56c1246755147bcec48e>
- <https://github.com/h2database/h2database/commit/b24aa46f48904ce64443f8f4353d70a2eed09037>
- <https://github.com/h2database/h2database/security/advisories/GHSA-h376-j262-vhq6>
## Setup
Start a spring-boot with h2 database 2.0.204:
```
docker compose up -d
```
After started the container, the spring-boot is listening on `http://your-ip:8080`, the management page is `http://your-ip:8080/h2-console/` by default.
## Vulnerability Reproduce
Before reproducing this issue, we can confirm that the payload in [CVE-2018-10054](../CVE-2018-10054) is not exploitable because in-memory database is disabled after 1.4.197:
![](1.png)
The H2 console after version 1.4.197 added a new [`-ifNotExists` option](https://github.com/h2database/h2database/pull/1726) that disable remote database creation by default. So you are unable to authenticate the H2 console without a known database file, such as in-memory database.
However, the H2 console still supports [JNDI injection](https://www.veracode.com/blog/research/exploiting-jndi-injections-java), which can be used to execute arbitrary code.
Simply use the [Java-Chains](https://github.com/vulhub/java-chains) to exploit the vulnerability.
First, generate the malicious JNDI URL by using the `JNDI/JNDIResourceRefPayload` module (don't forget to input the command you want to execute):
![](2.png)
Then, go to the H2 Web console login page, enter `javax.naming.InitialContext` as the Driver class, and the JNDI URL generated by Java-Chains as the JDBC URL.
![](3.png)
As you can see, the command has been executed successfully:
![](4.png)

View File

@@ -0,0 +1,51 @@
# H2 Database Web 控制台未授权JNDI注入RCE漏洞CVE-2021-42392
H2 Database是一个快速、开源的基于Java的关系型数据库管理系统RDBMS可用于嵌入式集成在Java应用中和客户端-服务器模式。
当Spring Boot集成H2 Database时如果设置如下选项将会启用Web管理页面
```
spring.h2.console.enabled=true
spring.h2.console.settings.web-allow-others=true
```
1.4.206之前版本的H2 Database管理页面支持通过JNDI加载JDBC驱动攻击者可以利用JNDI注入实现远程代码执行。
参考链接:
- <https://jfrog.com/blog/the-jndi-strikes-back-unauthenticated-rce-in-h2-database-console/>
- <https://mp.weixin.qq.com/s?__biz=MzI2NTM1MjQ3OA==&mid=2247483658&idx=1&sn=584710da0fbe56c1246755147bcec48e>
- <https://github.com/h2database/h2database/commit/b24aa46f48904ce64443f8f4353d70a2eed09037>
- <https://github.com/h2database/h2database/security/advisories/GHSA-h376-j262-vhq6>
## 环境搭建
执行如下命令启动一个集成了H2 Database 2.0.204版本的Spring Boot
```
docker compose up -d
```
容器启动后Spring Boot服务监听在`http://your-ip:8080`H2管理页面默认地址为`http://your-ip:8080/h2-console/`
## 漏洞复现
在复现本漏洞前,可以先确认[CVE-2018-10054](../CVE-2018-10054)中的payload已无法利用因为1.4.197之后内存数据库被禁用:
![](1.png)
1.4.197之后的H2控制台新增了[`-ifNotExists`选项](https://github.com/h2database/h2database/pull/1726)默认禁用远程数据库创建。因此攻击者无法通过未知数据库文件如内存数据库进入H2控制台。
但H2控制台依然支持[JNDI注入](https://www.veracode.com/blog/research/exploiting-jndi-injections-java),可用于执行任意代码。
我们可以直接使用[Java-Chains](https://github.com/vulhub/java-chains)来利用该漏洞。首先,使用`JNDI/JNDIResourceRefPayload`模块生成恶意JNDI URL记得填写你想执行的命令
![](2.png)
然后访问H2 Web控制台登录页将Driver class填写为`javax.naming.InitialContext`JDBC URL填写为Java-Chains生成的JNDI URL
![](3.png)
如图所示,命令已被成功执行:
![](4.png)

View File

@@ -0,0 +1,6 @@
services:
web:
image: vulhub/spring-with-h2database:2.0.204
ports:
- "8080:8080"
- "5005:5005"