RE: Disclosure of vulns and its legal aspects...



With the number of horror stories about disclosing vulnerabilities to large
companies, I would tread lightly. If it was a small company or personal
website they would probably thank you, this is not the case with the larger
companies.

As far as legality, I don't know. But I was always thought "testing some
websites as a personal research/leisure" without the owners permission can
land you in a world of hurt if they have a legal team.


-----Original Message-----
From: listbounce@xxxxxxxxxxxxxxxxx [mailto:listbounce@xxxxxxxxxxxxxxxxx] On
Behalf Of Dark Cold Ice
Sent: Tuesday, May 29, 2007 5:12 PM
To: pen-test@xxxxxxxxxxxxxxxxx; security-basics@xxxxxxxxxxxxxxxxx
Subject: Disclosure of vulns and its legal aspects...

Hi all,

It was earlier today whilst testing some websites as a personal
research/leisure time that i found a quite critical bug in a major
computer related website which will not be disclosured until all the
legal aspects of the disclosure process itself are dealt with.
After detecting the aforementioned vulnerability i was, like many have
been before, "jailed" between the decisions of reporting it or not, it
didn't take me long to decide to report it to the vendor as the flaw
itself was on it's website... My first step and only one so far was to
write the vendor the typical "praxis" e-mail saying that there MIGHT
be a vulnerability SOMEWHERE on their website and that i would like
carte blanche to investigate a bit more about it. I am now stuck with
3 thoughts, first of all, if the answer is no ( most common perhaps)
the vendor will be losing its chance to know where and what flaw is
it... will i be stuck with that and not be able to publicize it to the
security community?
Second thought, if the vendor says yes, i will report them the
vulnerability but, what entitles me the right to do it legally... a
simple e-mail would be enough perhaps...
Third and last thought, if they indeed agree to give me the chance to
test and report them the vulnerability i will only be entitled to
publicize it once solved, but even then, will it be legal to make a
full disclosure?

Thank you all in advance,

Darkcoldice

PS: What would the difference be between the US and UK laws on that
final aspect?

------------------------------------------------------------------------
This List Sponsored by: Cenzic

Are you using SPI, Watchfire or WhiteHat?
Consider getting clear vision with Cenzic
See HOW Now with our 20/20 program!

http://www.cenzic.com/c/2020
------------------------------------------------------------------------


------------------------------------------------------------------------
This List Sponsored by: Cenzic

Are you using SPI, Watchfire or WhiteHat?
Consider getting clear vision with Cenzic
See HOW Now with our 20/20 program!

http://www.cenzic.com/c/2020
------------------------------------------------------------------------



Relevant Pages

  • Open-Xchange Security Advisory 2013-03-13
    ... The vendor has chosen responsible full disclosure to publish security issue details. ... Vulnerability Type: Cross Site Scripting ... Internal reference: 24649 ...
    (Bugtraq)
  • Re: Using 0days as part of pen-test?
    ... the client the option to determine how the vendor gets notified. ... vulnerability information you discover during ... The legal issue isn't the disclosure process, you can act as "legal entity" ... security threats until the vendor release a patch. ...
    (Pen-Test)
  • [Full-disclosure] CORELAN-10-035 NolaPro Enterprise multiple vulnerabilities
    ... Vendor: Noguska LLC ... SQL Injection, Cross-Site Scripting, Information Disclosure ... Vulnerability discovered by: ekse ...
    (Full-Disclosure)
  • Re: Call to arms - INFORMATION ANARCHY
    ... Its one thing to prove to a Vendor they have a problem in their code. ... and its not resolved by keeping "Full Disclosure" alive. ... the Vendor for a vulnerability without accepting responsibility for your ... feed the feature versus security mentality of many Vendors. ...
    (NT-Bugtraq)
  • Re: Call to arms - INFORMATION ANARCHY
    ... Its one thing to prove to a Vendor they have a problem in their code. ... and its not resolved by keeping "Full Disclosure" alive. ... > the Vendor for a vulnerability without accepting responsibility for your ... > feed the feature versus security mentality of many Vendors. ...
    (NT-Bugtraq)