full-disclosure - Publicly Disclosing A Vulnerability

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Date: Wed Oct  5 19:47:00 2005
From: perrymonj at networkarmor.com (Josh Perrymon)
Subject: Publicly Disclosing A Vulnerability

Ok,

I have already worked with the Client and Vendor and the vendor is providing a free upgrade to the customer for no charge to correct the vulnerable issue. 
My focus is to protect the customer first...   The customer agreed that the vulnerability could be disclosed after they upgrade...

So I guess the only part of this I didn't care for was the vendor saying that they did not want me to release this information to the public.... I think it's because the client would get the upgrade for free instead of paying for it.

JP

________________________________________
From: full-disclosure-bounces@...ts.grok.org.uk [mailto:full-disclosure-bounces@...ts.grok.org.uk] On Behalf Of Josh Perrymon
Sent: Wednesday, October 05, 2005 10:52 AM
To: full-disclosure@...ts.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
Cell. 850.345.9186
Office: 850.205.7501 x1104