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.

Submit Comment Mode:
Name:
Subject:
Message:
 
  Enter the characters that appear above
 
Private first, then public, THEN publish exploit 2003-11-24
Anonymous
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 explo...

[ more ]  




 

Privacy Statement
Copyright 2009, SecurityFocus