Velocidex WinPmem versions 4.1 and below suffer from an Improper Input Validation vulnerability whereby an attacker with admin access can trigger a BSOD with a parallel thread changing the memory’s access right under the control of the user-mode application. This is due to verification only being performed at the beginning of the routine allowing the userspace to change page permissions half way through the routine. A valid workaround is a rule to detect unauthorized loading of winpmem outside incident response operations.
Metrics
Affected Vendors & Products
References
| Link | Providers |
|---|---|
| https://github.com/Velocidex/WinPmem/releases/tag/v4.1.dev1 |
|
History
Fri, 05 Sep 2025 09:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-20 |
Fri, 05 Sep 2025 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-367 |
Sat, 12 Jul 2025 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
epss
|
epss
|
Mon, 16 Dec 2024 16:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Mon, 16 Dec 2024 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Velocidex WinPmem versions below 4.1 suffer from an Improper Input Validation vulnerability whereby an attacker can directly communicate with the driver by accessing the \"\\\\.\\pmem\" device. From that point, it is possible to communicate with the driver via regular device operations, starting with a system of IOCTLs. To send specific orders to the driver, one can use IRP_MJ_DEVICE_CONTROL control code. This issue is remediated in version 4.1. | Velocidex WinPmem versions 4.1 and below suffer from an Improper Input Validation vulnerability whereby an attacker with admin access can trigger a BSOD with a parallel thread changing the memory’s access right under the control of the user-mode application. This is due to verification only being performed at the beginning of the routine allowing the userspace to change page permissions half way through the routine. A valid workaround is a rule to detect unauthorized loading of winpmem outside incident response operations. |
Mon, 16 Dec 2024 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Velocidex WinPmem versions below 4.1 suffer from an Improper Input Validation vulnerability whereby an attacker can directly communicate with the driver by accessing the \"\\\\.\\pmem\" device. From that point, it is possible to communicate with the driver via regular device operations, starting with a system of IOCTLs. To send specific orders to the driver, one can use IRP_MJ_DEVICE_CONTROL control code. This issue is remediated in version 4.1. | |
| Title | WinPmem Improper Input Validation vulnerability | |
| Weaknesses | CWE-20 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: rapid7
Published: 2024-12-16T14:49:07.294Z
Updated: 2025-09-05T08:40:18.985Z
Reserved: 2024-11-07T16:33:46.948Z
Link: CVE-2024-10972
Updated: 2024-12-16T15:31:07.140Z
Status : Awaiting Analysis
Published: 2024-12-16T15:15:06.067
Modified: 2025-09-05T09:15:30.500
Link: CVE-2024-10972
No data.