I have a bug where a user can create a file anywhere.
This file:
1.can have any name/ext
2.will be empty
3.must not exist. E.g you can't create c:\windows\win.ini
4. You can't edit it
I can DOS.Other ideas you would like to share?
/cc: @SandboxBear , @decoder_it , @tiraniddo
-
Show this thread
-
This Tweet is unavailable.
-
Replying to @SandboxBear @decoder_it and
this is how I caused the DOS. I created an empty DLL in a folder of another win app. Whenever this app tries to load the empty dll, it crashes. Maybe I could try what you are suggesting. I could try and chain it with a missing dll & exploit the crashes. Thanks for your answer :-)
1 reply 0 retweets 1 like -
Replying to @gweeperx @SandboxBear and
If you just wanna DOS make cng.sys in Windows or system32. Bsod on boot :)
1 reply 0 retweets 1 like -
Replying to @jonasLyk @SandboxBear and
Ohhh... this was evil...
@jonasLyk you have answered with 6 tweets and i have learned 20 things. Thank you very very much for your answers. I appreciate it!pic.twitter.com/CRPndRnoUJ
1 reply 0 retweets 0 likes
:) Just happy to share weird cornercase knowledge. Another good one is inserting an 0xu00 in an manifest file(I aassme it have to be loaded by something running as SYSTEM, but havent tested) The really nasty ones that BSOD by just operning a specific filename I dont share though
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.