Linked by Thom Holwerda on Wed 15th Apr 2009 09:54 UTC
Permalink for comment 358634
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/25/13 0:45 UTC
Linked by Thom Holwerda on 05/24/13 23:59 UTC
Linked by Thom Holwerda on 05/24/13 22:33 UTC
Linked by Howard Fosdick on 05/24/13 21:41 UTC
Linked by Thom Holwerda on 05/24/13 14:44 UTC
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
More News »
Sponsored Links



Member since:
2005-07-26
Who is to blame for being compromised by an exploit for which a patch was released months before?

The admin. (which is quite often also the primary user in home systems)
Sure, Microsoft had code with an exploit. But they found it (or someone else pointed it out to them using responsible disclosure, hopefully) and they released a patch that was pushed out in updates.
There have been similar problems in the Linux world. Slapper, anyone? Who is responsible for getting hit by a Linux worm that has had a patch released months before?
I stand by my answer. The admin is responsible.
(as for who is responsible for repairing the code, if it the bad code is in mysql, then the mysql team is responsible to fix, but that is pretty obvious, eh?)