Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CVE-2023-44976 PoC — Hangzhou Shunwang Rentdrv2 安全漏洞

Source
Associated Vulnerability
Title:Hangzhou Shunwang Rentdrv2 安全漏洞 (CVE-2023-44976)
Description:Hangzhou Shunwang Rentdrv2是中国顺网科技(Hangzhou Shunwang)公司的一个应用软件。 Hangzhou Shunwang Rentdrv2 2024-12-24之前版本存在安全漏洞,该漏洞源于DeviceIoControl函数存在缺陷,可能导致进程终止。
Description
A vulnerable driver exploited by me (BYOVD) that is capable of terminating several EDRs and antivirus software in the market, rendering them ineffective, working for both x32 and x64(CVE-2023-44976).
Readme
# BadRentdrv2

A vulnerable driver exploited by me (BYOVD) that is capable of terminating several EDRs and antivirus software in the market, rendering them ineffective, working for both x32 and x64.

## How does it work?

Compile targeting the legacy x32 architecture for a wider attack range.

In an elevated command prompt(Admin), use the following command line:
```
BadRentdrv2.exe <PID>
```
This will terminate the protected process without any difficulty.

Note: In this proof of concept, I have only programmed it to terminate the process using the PID. It supports other methods such as terminating by the process name and terminating the process and its child processes by the parent process name. To do this, simply make a small modification, and it will work. Please read the proof of concept code to understand.

## Tests on the most well-known security systems in the market:

#### 360 Antivirus

![360 Antivirus teste](imgs/teste_poc_360_antivirus.gif)

#### Kaspersky Antivirus

![Kaspersky Antivirus teste](imgs/teste_poc_kaspersky_antivirus.gif)

#### Avast Antivirus

![Avast Antivirus teste](imgs/teste_poc_avast_antivirus.gif)

#### AVG Antivirus

![AVG Antivirus teste](imgs/teste_poc_avg_antivirus.gif)

#### Panda Antivirus

![Panda Antivirus teste](imgs/teste_poc_panda_antivirus.gif)

#### Windows Defender

![Windows Defender teste](imgs/teste_poc_windows_defender_antivirus.gif)

## Driver Hash

I published the vulnerability because I was unable to contact the developer company to report it

## Timeline
- Contact #1(Without response).
- Contact #2(Without response).
- Notified to Mitre about the lack of contact with the company and CVE issued to attempt contact.
- Contact #3 (Sent a last e-mail with the CVE number, with 14-days to response).
- Published(Without response).
- Some idiots from APT used it into malware's(on the same day i published) - Explained with a very cool article by [Unit42-Team](https://unit42.paloaltonetworks.com/agonizing-serpens-targets-israeli-tech-higher-ed-sectors/)(and their team have my respect because investigate and appoint it as a vulnerabilty on the driver too).
- An notification was sent to Microsoft's threat intelligence team.
- Microsoft send back an email thanking about the report.
- Driver and Company Account got blocked by Microsoft Threat Intelligence Team.
- Published on the "Microsoft recommended driver block rules".
- I didn't publish the CVE because the company didn't respond me and not like to force publication.

rentdrv2_x32 - 1aed62a63b4802e599bbd33162319129501d603cceeb5e1eb22fd4733b3018a3

rentdrv2_x64 - 9165d4f3036919a96b86d24b64d75d692802c7513f2b3054b20be40c212240a5
File Snapshot

[4.0K] /data/pocs/4e721f86104c7b4a84726db9d44460bc2f26bd9e ├── [4.0K] BadRentdrv2 │   ├── [4.0K] BadRentdrv2 │   │   ├── [9.6K] BadRentdrv2.cpp │   │   ├── [6.6K] BadRentdrv2.vcxproj │   │   ├── [1.2K] BadRentdrv2.vcxproj.filters │   │   ├── [ 165] BadRentdrv2.vcxproj.user │   │   ├── [245K] rentdrv2_32.hh │   │   └── [192K] rentdrv2_64.hh │   └── [1.4K] BadRentdrv2.sln ├── [4.0K] imgs │   ├── [761K] teste_poc_360_antivirus.gif │   ├── [491K] teste_poc_avast_antivirus.gif │   ├── [512K] teste_poc_avg_antivirus.gif │   ├── [548K] teste_poc_kaspersky_antivirus.gif │   ├── [1.1M] teste_poc_panda_antivirus.gif │   └── [1.7M] teste_poc_windows_defender_antivirus.gif ├── [ 34K] LICENSE └── [2.6K] README.md 3 directories, 15 files
Shenlong Bot has cached this for you
Remarks
    1. It is advised to access via the original source first.
    2. If the original source is unavailable, please email f.jinxu#gmail.com for a local snapshot (replace # with @).
    3. Shenlong has snapshotted the POC code for you. To support long-term maintenance, please consider donating. Thank you for your support.