4 ms·
I seem to remember just having some text copy+pasted into IRC channels used to send peoples anti virus software into meltdown.. but this was sometime like 2000-
by bobbles 12y ago
I seem to remember just having some text copy+pasted into IRC channels used to send peoples anti virus software into meltdown.. but this was sometime like 2000-2001
- duskwuff 12y agoFor a while, some security suites would freak out and terminate an IRC connection if they saw the text "start keylogger" show up. You could get people to drop by saying it in a channel, for instance.
- ygra 12y agoOr, more sneakily, by embedding it in your hostmask.
- TazeTSchnitzel 12y agohttp://bash.org/?13213 http://bash.org/?13213 Like this?
- duskwuff 12y agoWorse, actually. As I recall, it'd block access to the responsible IRC server until you rebooted the machine. But yes, kind of like that.
- deleted 12y ago[deleted]
- simcop2387 12y agoDCC SEND LOLLERCOPTER There were a few others, but that's the one i remember. the part after DCC SEND doesn't matter as long as it was longer than 8 characters i think it was.
- frik 12y agoIt was a bug in Linksys, Netgear routers that rebooted the device. bug report e.g. http://colloquy.info/project/ticket/531 http://colloquy.info/project/ticket/531
- thelsdj 12y agoI had a modem that would disconnect if someone typed: ATH0++ in IRC.
- mschuster91 12y agoDCC SEND startkeylogger or such combined both exploits. Ah, I had quite a fun with that a couple of years back. IIRC it still bites a couple of people on Freenode, but the most networks have auto-kick bots in place for these scriptkiddies.
- JimDabell 12y agoIf I remember correctly, it used to be the case that if you could get the string +++ATH0 transmitted to somebody in the clear, you could hang up their dialup connection because it was a control code for Hayes modems that ended up being standardised on. Badly written firmware in modems meant that this was often interpreted even when it wasn't transmitted in a control code context.
- beagle3 12y agoThere wasn't really a "control code context" - it was (2 second silence)+++(1 second silence) to switch to command mode, and then ATH to disconnect. Bad firmwares would also accept same from remote side, although supposedly it should only have come from the local side.
- spacemanmatt 12y agoBitCom, a trashy DOS based terminal program, would lower the signal on the DTR pin, which would hang up the modem instantly, when it saw the text, "NO CARRIER" on a line by itself. Obviously, that line got dropped in forums and chat rooms as the "word of the day for BitCom users" on a regular basis.
- thristian 12y agoActually, it wasn't "badly written firmware". Hayes modems actually looked for "+++", then a second or so of no traffic, before they would switch into command-mode, and that delay was patented. So "Hayes-compatible" modems would implement the system without the delay, and as a result were vulnerable to remote DoS.
- hosay123 12y agoTo extend this a little further, various brands of modems (at least Rockwell) supported it but came with it disabled by default. You could enable it before dialling up by setting an S register
- anonymfus 12y agoThis reminds me how the string %English% transferred via SMS crashed some old Siemens phones and GSM modules because of error in detection of embedded images. And how recently string سمَـَّوُوُحخ ̷̴̐خ ̷̴̐خ ̷̴̐خ امارتيخ ̷̴̐خ could crash some versions of iOS and OS X.
- deleted 12y ago[deleted]