Search: Home Bugtraq Vulnerabilities Mailing Lists Jobs Tools Beta Programs
Exploit Code on Trial
Kevin Poulsen, SecurityFocus 2003-11-23

Security pros gathering at a Stanford University Law School conference on responsible vulnerability disclosure Saturday harmonized on the principle that vendors should be privately notified of holes in their products, and given at least some time to produce a patch before any public disclosure is made. But there was pronounced disagreement on the question of whether or not researchers should publicly release proof-of-concept code to demonstrate a vulnerability.

Comments Mode:
Exploit Code on Trial 2003-11-24
Anonymous
Screw the vendors 2003-11-24
Anonymous (2 replies)
Screw the vendors 2003-11-25
Rodrigo Otaviano <rodrigo (at) otaviano (dot) com [email concealed]>
Exploit Code on Trial 2003-11-24
Bob Radvanovsky
Exploit Code on Trial 2003-11-24
Anonymous
Exploit Code on Trial 2003-11-24
TW
Private first, then public, THEN publish exploit 2003-11-24
Anonymous (1 replies)
Private first, then public, THEN publish exploit 2003-11-25
Anonymous
Hate to say this ... but that's what CERT was originally used for, and it simply didn't work.

It took months for vendors to actually fix problems. So some white/grey hats just got tired and decided to rapidly publish exploit code.

What motivation does a vendor have to fix code quickly? If it's not out in the public, then there is little to no motivation.

Just the report of a possible exploit will make black hats find the hole and create exploit code themselves, if they already hadn't found the problem first. So who benefits by allowing a vendor too much time to fix a problem?

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/articles/7511/23845#23845
Exploit Code on Trial 2003-11-25
Leif Ericksen
Exploit Code on Trial - final word 2003-11-25
Anonymous (1 replies)
Exploit Code on Trial 2003-11-25
Camel
Loss of money 2003-11-29
bl0rf
Exploit Code on Trial 2003-12-02
Anonymous
Exploit Code on Trial 2003-12-02
Anonymous







 

Privacy Statement
Copyright 2009, SecurityFocus