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)
First, notify the vendor privately and give them a reasonable amount of time to come out with a patch. Second, if the vendor is ignoring the problem, go public with the vulnerability, but do NOT publish exploit code yet. Only if the vendor publicly denies the vulenrability, or says "it's not explotiable", do you publish the exploit code.

Although this order of action delays the release of "white hat" exploit code, it will still get out if the vendor does nothing. The vendor just is given more than one chance (during private and public notification phases) to address the problem first...

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/articles/7511/23838#23838
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