(Mine's 30 bytes at the moment but I have a script scanning for shorter ones. I will let you know how when its finished).
-
-
Show this thread
-
Here's a hint: http://seclists.org/fulldisclosure/2004/Oct/64 …
Show this thread
End of conversation
New conversation -
-
-
"rundll32 adsldpc intcmp" => 23 bytes to a type confusion that causes an access violation. Scanner is still going through the list of dlls and exports to find a shorter one.
Show this thread -
Batch script to enumerate dlls on a folder, `dumpbin` to enumerate exports in each dll, `BugId` to start "rundll32 <dll> <export>" => a plethora of different types of crashes.
Show this thread -
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 -
-
-
They fixed it I believe, but I always liked the Windows XP cmd.exe crasher I found via laggy rdp : dir /oddddddpic.twitter.com/2KjN3KFYo4
- End of conversation
New conversation -
-
-
“powershell start wininit”
-
No need for 'start'. :)
End of conversation
New conversation -
-
-
1) Debug-Process
$pid 2) while(1){$a+=,$a} 3) [Runtime.InteropServices.Marshal]::WriteByte(0,0) 4) ri c:\ -rec -force 5) ri hklm:\ -rec -forceThanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
You could make a book if assembler/debug was still in "vanilla"
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I've this fusion cache thingy
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.