dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2024-36056

MEDIUM · 5.4 CVSS v3.1 Published 2024-05-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Hw64.sys in Marvin Test HW.exe before 5.0.5.0 allows unprivileged user-mode processes to arbitrarily map physical memory via IOCTL 0x9c406490 (for IoAllocateMdl, MmBuildMdlForNonPagedPool, and MmMapLockedPages), leading to NT AUTHORITY\SYSTEM privilege escalation.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Hw64.sys kernel driver in Marvin Test HW.exe before version 5.0.5.0 contains an insecure IOCTL handler (0x9c406490) that allows unprivileged user-mode processes to arbitrarily map physical memory via exposed kernel functions IoAllocateMdl, MmBuildMdlForNonPagedPool, and MmMapLockedPages, enabling local privilege escalation to NT AUTHORITY\SYSTEM.

MitigationUpdate Marvin Test HW.exe to version 5.0.5.0 or later to obtain the patched Hw64.sys driver, and restrict driver access to privileged users until the update is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate Marvin Test HW.exe and check its version
    Find the Marvin Test HW.exe executable on the system (common paths: C:\Program Files\Marvin Test\ or C:\Program Files (x86)\Marvin Test\). Right-click the file, select Properties, and check the File Version field. Compare this version number to 5.0.5.0.
    Affected if The installed version is earlier than 5.0.5.0 or the version cannot be determined.
  2. Locate and verify Hw64.sys driver version
    Find Hw64.sys in the driver directory (typically in the Marvin Test installation folder under a Driver or Sys subfolder). Right-click the file, select Properties, and check the File Version or Product Version. Compare to the version bundled with Marvin Test HW.exe 5.0.5.0.
    Affected if The driver version is older than the version shipped with 5.0.5.0.
  3. Check if the driver is loaded
    Open an elevated command prompt and run: sc query Hw64.sys or use drivers.exe (from Sysinternals) to list loaded drivers and check if Hw64.sys appears in the list.
    Affected if The Hw64.sys driver is currently loaded on the system.
  4. Identify the vulnerable IOCTL handler
    Use a tool such as WinObj or Process Monitor to observe kernel object namespace accesses, or use a driver analysis tool to inspect the IOCTL codes exported by Hw64.sys. Specifically look for IOCTL code 0x9c406490.
    Affected if IOCTL 0x9c406490 is exposed and accessible from user-mode.
  5. Verify non-privileged user access to the driver
    Attempt to open a handle to the driver device from a non-administrator account using a tool like WinObj or by writing a simple test application that calls CreateFile on the device path (\\.\Hw64). If the handle is obtained successfully, the vulnerability is exploitable.
    Affected if Unprivileged users can obtain a handle to the driver and send IOCTL requests.

The system is affected if Marvin Test HW.exe version is earlier than 5.0.5.0, the Hw64.sys driver is loaded, and unprivileged users can access the vulnerable IOCTL 0x9c406490 handler.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Marvin Test HW.exe to version 5.0.5.0 or later to obtain the patched Hw64.sys driver, and restrict driver access to privileged users until the update is applied.

Recommended fix High confidence

Marvin Test HW.exe 5.0.5.0 or later

  1. 1. Identify the current version of Marvin Test HW.exe and Hw64.sys driver installed on the system
  2. 2. Navigate to the official Marvin Test website or vendor distribution channel
  3. 3. Download Marvin Test HW.exe version 5.0.5.0 or later
  4. 4. Before installation, ensure you have appropriate backup and administrative privileges
  5. 5. Install the updated version following standard vendor installation procedures
  6. 6. Verify the new version is installed correctly and the Hw64.sys driver is updated
  7. 7. Test that the application functions normally with the new driver
Caveat Review vendor release notes for any functionality changes between your current version and 5.0.5.0

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36056 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-36056 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data