CVE-2024-10972

WinPmem Improper Input Validation vulnerability

Published Dec 16, 2024 CVSS 3.1 · 7.3 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

No analysis available yet

Remediation

No remediation available yet

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2024-33562 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.
History
Type Values Removed Values Added
Weaknesses CWE-20
Type Values Removed Values Added
Weaknesses CWE-367
Type Values Removed Values Added
Metrics epss

{'score': 0.00031}

epss

{'score': 0.00034}

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

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.
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

{'score': 7.3, 'vector': 'CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:H'}

Subscriptions

No data.

Weaknesses
  • CWE-367

    Time-of-check Time-of-use (TOCTOU) Race Condition

Sources

Status
PUBLISHED
Assigner
rapid7
Published
Updated
Sep 5, 2025, 8:40 AM
Reserved
Nov 7, 2024, 4:33 PM
Status
Deferred
Published
Dec 16, 2024, 3:15 PM
Modified
Jun 17, 2026, 6:56 AM