dbcve.org
Incorrect AuthorizationWeakness · CWE-863

CVE-2024-36055

MEDIUM · 5.5 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 →
57/100
Remediation priority · Elevated
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 with read/write access via the MmMapIoSpace API (IOCTL 0x9c40a4f8, 0x9c40a4e8, 0x9c40a4c0, 0x9c40a4c4, 0x9c40a4ec, and seven others), leading to a denial of service (BSOD).

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

Hw64.sys kernel driver in Marvin Test HW.exe before 5.0.5.0 contains multiple IOCTL handlers (0x9c40a4f8, 0x9c40a4e8, 0x9c40a4c0, 0x9c40a4c4, 0x9c40a4ec and seven others) that allow unprivileged user-mode processes to arbitrarily map physical memory with read/write access via the MmMapIoSpace API, leading to system crashes (BSOD).

MitigationUpgrade Marvin Test HW.exe to version 5.0.5.0 or later which contains the patched driver. Until then, restrict access to the software and associated driver to trusted administrators only.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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 installation directory
    Search for Marvin Test HW.exe in typical installation paths such as C:\Program Files\Marvin Test\ or C:\Program Files (x86)\Marvin Test\, or use PowerShell: Get-ChildItem -Path 'C:\Program Files*' -Recurse -Filter 'Marvin Test HW.exe' -ErrorAction SilentlyContinue
    Affected if The executable is found at any version before 5.0.5.0 or if version cannot be determined
  2. Determine installed version of Marvin Test HW.exe
    Right-click the executable, select Properties, then view the Details tab for Product Version, or use PowerShell: (Get-Item 'C:\Program Files\Marvin Test\Marvin Test HW.exe').VersionInfo.ProductVersion
    Affected if Version displayed is lower than 5.0.5.0 (for example, 5.0.4.0, 5.0.3.0, etc.)
  3. Locate Hw64.sys driver file
    Search for Hw64.sys in the Marvin Test installation directory or system driver folders (C:\Windows\System32\drivers\), or use PowerShell: Get-ChildItem -Path 'C:\' -Recurse -Filter 'Hw64.sys' -ErrorAction SilentlyContinue
    Affected if The driver file exists on the system (indicating the vulnerable driver component is present)
  4. Check if Hw64.sys driver is currently loaded
    Open Command Prompt as Administrator and run: sc query Hw64sys or driverquery /v | findstr Hw64, or in PowerShell: Get-Service -Name '*Hw64*' -ErrorAction SilentlyContinue
    Affected if The driver shows a status of Running or Started, meaning it is actively loaded in kernel mode

A user is affected if Marvin Test HW.exe version is below 5.0.5.0 AND the Hw64.sys driver is present or loaded on the system, as this combination enables the vulnerable IOCTL handlers to be exploited by unprivileged processes.

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

Upgrade Marvin Test HW.exe to version 5.0.5.0 or later which contains the patched driver. Until then, restrict access to the software and associated driver to trusted administrators only.

Recommended fix Moderate confidence

Marvin Test HW.exe version 5.0.5.0 or later

  1. Obtain Marvin Test HW.exe version 5.0.5.0 or later from the official vendor (www.marvintest.com)
  2. Uninstall the current version of Marvin Test HW.exe from the system
  3. Install the updated version 5.0.5.0 or later that includes the fixed Hw64.sys driver
  4. Verify the driver version by checking the file properties of Hw64.sys to confirm the fix is applied
  5. Restart the system if required to load the updated driver
Caveat Driver updates typically have low risk of breaking changes, but ensure compatibility with your test equipment before production deployment

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-36055 — 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-36055 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