Skip to main content
← All vulnerabilities
CVE-2026-116776EUVD-2026-112149GHSA-CFRV-C9Q2-7CR3

USB Test: Heap-based Buffer Overflow in getSectorSize via untrusted DISK_GEOMETRY.BytesPerSector leads to RCE/DoS

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 1.1.5
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: poc
  • Automatable: no
  • Technical impact: partial

Summary

USB Test, a Windows command-line tool for checking USB flash drives, is affected before version 1.1.5. A maliciously crafted USB storage device can crash the elevated application or potentially allow arbitrary code execution when a user runs a drive test.

Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.

Read the original description

USB Test is a lightweight Windows CLI utility for verifying sector integrity and detecting overreported capacity on USB flash drives. Prior to version 1.1.5, getSectorSize() in USB Test/src/driveinfo.cpp trusts DISK_GEOMETRY.BytesPerSector returned by IOCTL_DISK_GET_DRIVE_GEOMETRY without checking whether the call succeeded or enforcing size bounds. USB Test/src/drivetest.cpp uses the value for division and to size a heap buffer before memcpy(buffer.data(), &sector, 8), so a physically connected malicious USB storage device can report a value below eight bytes and cause repeated out-of-bounds writes, or report zero and cause a divide-by-zero denial of service when a user starts a drive test. The heap corruption can crash the elevated application and may permit arbitrary code execution. This issue is fixed in version 1.1.5.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: partial

  4. Record last updated

Affected versions

  • n-romanovich usb-test

    fixed in 1.1.5

References 3

GitHub · n-romanovich/usb-test