CVE-2024-36054
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 · uneditedHw64.sys in Marvin Test HW.exe before 5.0.5.0 allows unprivileged user-mode processes to arbitrarily read kernel memory (and consequently gain all privileges) via IOCTL 0x9c4064b8 (via MmMapIoSpace) and IOCTL 0x9c406490 (via ZwMapViewOfSection).
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 confidenceThe Hw64.sys kernel driver in Marvin Test HW.exe before version 5.0.5.0 contains an arbitrary kernel memory read vulnerability. Unprivileged user-mode processes can send IOCTL codes 0x9c4064b8 (via MmMapIoSpace) and 0x9c406490 (via ZwMapViewOfSection) to map kernel memory into user space, enabling privilege escalation to SYSTEM level.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Marvin Test HW.exe installation pathSearch for 'Marvin Test HW.exe' in typical locations: C:\Program Files\Marvin Test\, C:\Program Files (x86)\Marvin Test\, or use 'Get-ChildItem -Path C:\ -Recurse -Filter "Marvin Test HW.exe" -ErrorAction SilentlyContinue' to locate itAffected if The file exists but version is below 5.0.5.0 or version cannot be determined
-
Check Marvin Test HW.exe file versionRight-click the executable, select Properties, then Details tab to view File Version; alternatively use PowerShell: (Get-Item "C:\Path\To\Marvin Test HW.exe").VersionInfo.FileVersionAffected if File version is missing, not displayed, or lower than 5.0.5.0
-
Locate and verify Hw64.sys driver versionFind Hw64.sys in the Marvin Test installation directory (typically under Program Files\Marvin Test\ driver folder); check file version via Properties or PowerShell: (Get-Item "C:\Path\To\Hw64.sys").VersionInfo.FileVersionAffected if Driver version is missing or lower than the version bundled with 5.0.5.0 of the main software
-
Confirm driver is currently loadedOpen Command Prompt as Administrator and run 'sc query Hw64' or 'driverquery /v | findstr -i Hw64' to check if the driver service is activeAffected if Driver is loaded and running on a system with vulnerable software version (below 5.0.5.0)
A system is affected if Marvin Test HW.exe version or Hw64.sys driver version is below 5.0.5.0 and the driver is loaded in memory.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade Marvin Test HW.exe to version 5.0.5.0 or later to obtain the patched Hw64.sys driver. Restrict user access to systems running the affected software until patched, as the attack requires local code execution capability.
5.0.5.0 or later
- Identify the currently installed version of Marvin Test HW.exe
- If version is before 5.0.5.0, obtain the latest version from the vendor (www.marvintest.com)
- Upgrade Marvin Test HW.exe to version 5.0.5.0 or later
- Verify the Hw64.sys driver version matches the updated application version
- Reboot the system to ensure the new driver loads properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2024-36054 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-36054 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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