• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Using ping.exe to crash win2k? really?

Q

Quad

Golden Member
i remember a while ago someone posted a thread that showed how ping.exe can crash win2k...
just wondering if anyone remembers how it is done?

thx in advance
 

To find out the ping command, at DOS prompt type: ping /?

The Ping 65468 bytes package size that you ask for is an old trick which has been fixed by most/all OSes.

eg. At command prompt type: ping -t -l 65468 192.168.1.1
 
hmm
actually i remember that it took a few steps. first you had to ping some ip, using a specific syntax, and then there was a step after that.

anyone remember?
thx in advance
 
Are you talking about the "ping of death"? If so then the post above has it covered. You could ping a stating (MS operating systems in particular) with a size that would cause some kind of overflow in the IP stack and crash the box.

But that has been fixed years back. Any decent security will block your ping anyways. Maybe search for ping of death on google?
 
i remember that it was specifically for win2k. it would cause a system reboot if i remember correctly. :\
 
well i found it 😛
seems pretty simple really

you ping any host, then rapidly hit f7 and enter back and forth
comp reboots
 
wow, never heard of that one until now and it worked like a champ on this win2k workstation, insta-BSOD and reboot! lol

remember the Start-Run-> c:\con\con bug that made Windows 98 crash ? you could even (i think) make a simple link on a webpage that tried to access c:\con\con and make it crash



<HTML>
<BODY>
<A HREF="c:\con\con">crashing IE</A>
<!-- or nul\nul, clock$\clock$ -->
<!-- or aux\aux, config$\config$ -->
</BODY>
</HTML>

 


<< well i found it 😛
seems pretty simple really

you ping any host, then rapidly hit f7 and enter back and forth
comp reboots >>


That works for any command that takes time to execute. It has to do with overflowing the command buffer of the system, causing a pointer mangling which causes the reboot. It is a trivial DoS, and really not worth anything, as there are plenty of other ways to harm a system when you are sitting at it.

RagManX
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top