RE: Publicly Disclosing A Vulnerability

["Adriel Desautels" <adesautels () comcast net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Interesting, 
    I remember back when KF and I were running SNOsoft we executed a
research project against HP's Tru64. We contacted the vendor (HP) in
good faith and provided them with information regarding the
vulnerabilities that we'd discovered. The vendor immediatley
attempted to quash our research in an attempt to either save face or
save dollars, still not sure which, but the end result was some
serious turmoil and a lot of good and bad press for both sides.  If
you are concerned with your public/business image then I'd suggest
that you consider disclosure without credit as suggested by xyberpix.
My personal opinion is in support of disclosing the information as I
feel that it will help the people that know how to protect
themselves, protect themselves. 
 
- -Adriel


________________________________

        From: full-disclosure-bounces () lists grok org uk
[mailto:full-disclosure-bounces () lists grok org uk] On Behalf Of Josh
Perrymon
        Sent: Wednesday, October 05, 2005 10:52 AM
        To: full-disclosure () lists grok org uk
        Subject: [Full-disclosure] Publicly Disclosing A Vulnerability
        
        

        Ok,

         

        I believe in working with the Vendor to inform then of vulnerable
software upon finding it in the wild so on.

        But I have a question.

         

        While performing a pen-test for a large company I found a directory
transversal vulnerability in a search program-

        I used Achilles and inserted the DT attack in a hidden field and
posted it to the web server. This returned the win.ini..

        Cool..

         

        Well. I called the company up and got the lead engineer on the
phone.. He seemed a little pissed.

        He told me that they found the hole internally a couple months ago
but they don't want it public and they said I should not tell anyone
about it because they don't want their customers at risk.

         

        So I ask the list- what is more beneficial to the customer? Not
publicly disclosing the risk and hoping that they follow the
suggestions of the vendor to upgrade?  Or waiting 30 days and send it
out?

         

         

         

        Joshua Perrymon

        Sr. Security Consultant

        Network Armor

        A Division of Integrated Computer Solutions

        perrymonj( at )networkarmor.com <mailto:perrymonj () networkarmor com> 

        Cell. 850.345.9186

        Office: 850.205.7501 x1104

         


-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1
Comment: http://www.secnetops.com

iQA/AwUBQ0QcaJNLRT/rHZe1EQJ3+wCgzJRX8HT8VyOh3iLa5003Gelp/4wAni38
kUHdtMmiEFdUVHmq60HGL+jd
=F1BG
-----END PGP SIGNATURE-----

Attachment: PGPexch.htm.pgp
Description:

_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/