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 definately should stay. Some descriptions of how the vulnerability works gets fudged as it is passed along. I trust exploit code more than the description of how it's done. Besides that, the code let's you get dirty with the vulnerability and shows you exactly how to do it. Once you know what it does, you can fix it in seconds. Another thing, vendors do not seem to fix things unless they are pushed to do so. They will just wait and wait until somebody publishes the code.

[ reply ]

Link to this comment: http://www.securityfocus.com/comments/articles/7511/23835#23835
Exploit Code on Trial 2003-11-24
TW
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