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 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 threadThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
so what would be the acceptable error handling behavior for you in that layer?
-
Error handling would be a fool's errand. rundll32's design is missing sanity checks that make sure both the DLL and the function were designed to work in Rundll32. e.g. a special marker in the DLL could be checked before loading it to prevent these crashes.
End of conversation
New conversation -
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.