Sign in to follow this  
Followers 0
logcomptechs

Overload a EXE?

17 posts in this topic

Wondering if anyone had any ideas on how to overload a .exe and crash it. I do not want to use ProcessClose and I was looking into _WinAPI_WriteProcessMemory but not sure how to use it. If anyone else has any ideas that would be awesome.

Thanks!

Share this post


Link to post
Share on other sites



Wondering if anyone had any ideas on how to overload a .exe and crash it. I do not want to use ProcessClose and I was looking into _WinAPI_WriteProcessMemory but not sure how to use it. If anyone else has any ideas that would be awesome.

Thanks!

Why exactly are you wanting to do this? What legit reason could you possibly have for wanting to crash an .exe?


"The true measure of a man is how he treats someone who can do him absolutely no good."

Share this post


Link to post
Share on other sites

Why exactly are you wanting to do this? What legit reason could you possibly have for wanting to crash an .exe?

To recreate a error, for testing purposes, but I am not sure how to make it crash every time. Was thinking about filling up the memory with random numbers or something, but I do know.

Share this post


Link to post
Share on other sites

search the forum... it's been done before


Only two things are infinite, the universe and human stupidity, and i'm not sure about the former -Alber EinsteinPractice makes perfect! but nobody's perfect so why practice at all?http://forum.ambrozie.ro

Share this post


Link to post
Share on other sites

Wondering if anyone had any ideas on how to overload a .exe and crash it. I do not want to use ProcessClose and I was looking into _WinAPI_WriteProcessMemory but not sure how to use it. If anyone else has any ideas that would be awesome.

Thanks!

http://www.autoitscript.com/forum/index.php?showtopic=90837

Share this post


Link to post
Share on other sites

The problem with trying to crash an application is that it really depends on the application itself. Many applications will prevent out-of-process memory writes.

Why not figure out what is causing the crash and then tracing the program through that kind of problem.

Share this post


Link to post
Share on other sites

Use CreateRemoteThread and pass NULL as the start address of the new thread. Should crash most apps.


Broken link? PM me and I'll send you the file!

Share this post


Link to post
Share on other sites

Thanks for all the suggestions guys!

Use CreateRemoteThread and pass NULL as the start address of the new thread. Should crash most apps.

Where is this found in the Help File?

Share this post


Link to post
Share on other sites

Did not think so, been looking couldn't find anything even close to that. Any other suggestions?

Share this post


Link to post
Share on other sites

Did not think so, been looking couldn't find anything even close to that. Any other suggestions?

Why would you even think it should be in the helpfile?

The Helpfile is about explaining AutoIt3, its Keywords, Functions and Standard UDF's , not about crashing programs which is questionable in the first place as far as I am concerned.

Jos


Visit the SciTE4AutoIt3 Download page for the latest versions        Beta files                                                          Forum Rules
 
Live for the present,
Dream of the future,
Learn from the past.
  :)

Share this post


Link to post
Share on other sites

DllCall("binkw32.dll", "int", "CreateRemoteThread", "null","null")

I did that, but it does not do anything, any thoughts?

Share this post


Link to post
Share on other sites

HANDLE CreateRemoteThread(

    HANDLE  hProcess,   // handle to process to create thread in  
    LPSECURITY_ATTRIBUTES  lpThreadAttributes,  // address of thread security attributes 
    DWORD  dwStackSize, // initial thread stack size, in bytes
    LPTHREAD_START_ROUTINE  lpStartAddress, // address of thread function 
    LPVOID  lpParameter,    // address of argument for new thread  
    DWORD  dwCreationFlags, // creation flags 
    LPDWORD  lpThreadId     // address of returned thread identifier 
   );

It's failing to preform the call so it's not calling anything, and 'null' is meant to be [type:value] 'ptr', '', I guess.

Share this post


Link to post
Share on other sites

Why would you even think it should be in the helpfile?

The Helpfile is about explaining AutoIt3, its Keywords, Functions and Standard UDF's , not about crashing programs which is questionable in the first place as far as I am concerned.

Jos

@monoceres and Authenticity

.... Why would you even think it should be in the helpers/MVP's spectrum!... after a post like that from Jos

I could see this one from the start! Threads like this can create MORE problems with malicious programs and Anti-Virus companies... There is enough problems already, That I am fighting everyday!

Yes, EVERYDAY!

8)


NEWHeader1.png

Share this post


Link to post
Share on other sites

Come on guys, use your brains. Here's your first clue: Arbitrarily crashing a program is not the same thing as reproducing an error rendering the whole idea pointless.

Anyway, thread locked, we don't need this shit discussed here.

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  
Followers 0