SOLVED native medium 2026-09-22
CubisVision — KeyAuth-style native auth
target: native x64 DLL (MSVC C++) // platform: windows
HTTP auth with an attestation challenge and a violation log. The network was not the weak point; the verdict compare was.
| RESULT | patched copy, 6 bytes differ, length unchanged |
| TECHNIQUES | static analysis · Capstone disassembly · verdict compare patch · export-table preserved |
| PUBLISHED | 2026-11-19 |
!! WHAT I FOUND !!
- Auth flow: init, license, periodic check, plus a log call that ships violations back to the auth service.
- Hardware fingerprint derived from the C: volume serial plus two more inputs.
- Verdict compare inside the module is the single point that matters; six bytes on it.
- All four exports still behave after patching, so the module remains droppable.
MY VERDICT:
An auth service only helps if the client trusts its answer correctly. That trust is a compare, and a compare is bytes.
Published as proof of the finding. The check, the failure and the reproduction go on the record.
Client engagements are named only with written permission.