full-disclosure - RE: MS SQL WORM IS DESTROYING INTERNET BLOCK PORT 1434!

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

From: benjamin at seattlefenix.net (Benjamin Krueger)
Subject: RE: MS SQL WORM IS DESTROYING INTERNET BLOCK PORT 1434!

* Jason Coombs (jasonc@...ence.org) [030125 16:49]:
> Bank of America should never have allowed their ATM network to rely on
> routes that could be impacted by non-ATM network computer systems.
> 
> That Sapphire might have had this effect makes the sensibility behind
> writing and releasing it even more apparent, if this was in fact defensive
> work of a government agency as my speculation suggested.
> 
> Jason Coombs
> jasonc@...ence.org
> 
> -----Original Message-----
> From: Richard M. Smith [mailto:rms@...puterbytesman.com]
> Sent: Saturday, January 25, 2003 1:11 PM
> To: jasonc@...ence.org; 'Jay D. Dyson'; 'Bugtraq'; 'Full-Disclosure'
> Subject: RE: MS SQL WORM IS DESTROYING INTERNET BLOCK PORT 1434!
> 
> 
> However, this worm might not be so harmless as it appears because of
> collateral damage:
> 
>    Bank of America ATMs Disrupted by Virus
> 

It's a little early to be assuming that the ATMs were gummed up by
network route congestion, isn't it? I find it entirely possible that
their datacenter where the transactions are processed was the real
scene of the outage, and not the individual ATMs or their routes.

-- 
Benjamin Krueger