CHALLENGE: What's the shortest Windows command-line you know that causes an unhandled exception in a Windows process? The command should start and crash a new process or crash an existing process. The exception can by anything that's obviously unintended (AV, OOM, breakpoint).
-
-
rundll32 advapi32 ReportEventW => NULL pointer rundll32 apphelp SdbQueryName AAAAAAA... => buffer overflow rundll32 advapi32 CopySid AAAAAA... => out-of-bounds read rundll32 AppVIntegration Initialize => read after free rundll32 advapi32 RegCloseKey => invalid handle ...
Show this thread -
... rundll32 advapi32 LsaManageSidNameMapping AAAAAAAA => read from 0x4141414141414141 (x64) rundll32 AppxApplicabilityEngine ?EmptyDecisionIndex@IDecisionInfo@Resources@Microsoft@@2HB => invalid handle ... and I've only scanned dlls whose name starts with "a" so far :)
Show this thread
End of conversation
New conversation -
-
-
Step 2: finding software that makes calls to these functions Step 3: creating PoCs that cause these calls to be executed Step 4: Cocktails in Maui
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.