Image
 
linkedin_logo.png rss_logo.jpg
twitter_logo.png youtube_logo.jpg
Latest Additions
 
EH-Net Login
Welcome Guest.






Lost Password?
No account yet? Register
Who's Online
We have 37 guests and 2 members online
 
Advertisement

You are here: Home arrow Ethical Hacking Discussions and Related Certificationsarrow Network Pen Testingarrow Which disclosure philosophy?
EH-Net
May 18, 2013, 01:31:41 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Go back to The Ethical Hacker Network Online Magazine Home Page
 
   Home   Help Calendar Login Register  
Pages: [1]   Go Down
  Print  
Author Topic: Which disclosure philosophy?  (Read 3019 times)
0 Members and 1 Guest are viewing this topic.
UNIX
Hero Member
*****
Offline Offline

Posts: 1234


View Profile
« on: July 09, 2009, 02:33:27 AM »

Hello,
lately I had some discussions about disclosure philosophies. Although I am currently not really into any big exploit development scene I am still interested in this area. I would like to know if you follow any strict methodology in the disclosure process, and how you think on the moral and ethical site of this.

I have found a similar thread on this topic but which focuses more on the problems regarding certifications. Still interesting and may be read.

Personally I don't follow any strict rules as I think it depends on the case itself. Full disclosure, which is probably best known from H D Moore, is certainly important to push and force companies to supply patches and updates. Also if a vuln. was found which is not public yet, it doesn't mean that no one else is aware of it. But it also means that this information is available for everyone, although not everyone is patching it (if someone is aware of a critical hole in her system she will probably fix it, but often people with little computer knowledge are not aware of it, although it is well-known).
Another fact I like in full-disclosure is that vendors probably have to do something in order to fix the vulnerability to not lose any customers/ clients and "face", however, I have often experienced that companies don't even reply if they got informed first privately and got some time to fix the problem. Also I experienced that companies replied in a very angry manner and threatened the person who found the security issue with a sue when she publish her findings.

Although there are many advantages in full disclosure there are also disadvantages. When an exploit is released for some very critical systems it may cause huge damage before a patch can be supplied. Because of this reason I think that it is good in general (again, I think there is no methodology to apply for every case) to give first the information to the manufacturer (responsible disclosure) and publish it then after a certain period of time to the public (is there any guideline on how long to wait actually? Wikipedia writes about fourteen to thirty days but I read on some other websites about six months).

I would like to know how other EH-Netters think about this and if you stick to a certain routine..hope to have a little virtual discussion too. Smiley
« Last Edit: July 09, 2009, 02:35:47 AM by awesec » Logged
ElCapitan
Newbie
*
Offline Offline

Posts: 28


Unanimous FTP: the #1 threat to copyrights!


View Profile
« Reply #1 on: July 10, 2009, 11:35:18 PM »

Disclosure to the vendor is noble, however, as you said vendors may reply in a very angry and threatening manner.

Personally, if identifying the vuln involved violating the EULA, I would not disclose it to the vendor. It wouldn't be worth the personal risk. One would also have to be careful of not violating other laws. Some the EFF mentioned:

  • Computer Fraud and Abuse Act
  • Anti-Circumvention Provisions of the DMCA
  • Copyright law

If it seemed extremely important to disclose to the vendor (even in violation of the above), I would go to great lengths to remain anonymous.

I'm not experienced in the exploit development scene anyway, so this is all hypothetical.
« Last Edit: July 11, 2009, 12:01:24 AM by ElCapitan » Logged

CISSP, Security+, CEH, OPP, et alii
timmedin
Sr. Member
****
Offline Offline

Posts: 469



View Profile WWW
« Reply #2 on: July 14, 2009, 06:29:16 PM »

I prefer a hybrid approach...

I would prefer vendors be given a chance to resolve the issue, if they don't take care of it in a reasonable amount of time then public disclosure lets everyone take steps to mitigate the issue.

Some companies (becoming fewer) attack the person who found the issue. In that case I would suggest the same as ElCapitan that you release the issue but maintain anonymity.

I understand that many would disagree with me since this topic seems to be as close to a a religious debate as PCI.
Logged

twitter.com/timmedin | http://blog.securitywhole.com
UNIX
Hero Member
*****
Offline Offline

Posts: 1234


View Profile
« Reply #3 on: July 15, 2009, 12:47:36 AM »

I wasn't sure if I should ask this question, but as it concerned me and this is certainly a place in which it can be asked and good answers can be expected, I did. Also I tried to not ask on which would be the best or most ethical at all, but about your personal opinions on it.

Thanks for your replies, much appreciated. Smiley

I think some vendors misinterpret a report and see it as some kind of personal attack, unfortunately. Normally one would think that they should be happy if a bug or vuln. was found as it should result in bugfixes and updates which eventually conduct to a better (more secure) product. Maybe they are afraid of the possible results, which are not only work/ effort to fix the issues and spend money on it.
Logged
Pages: [1]   Go Up
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.18 | SMF © 2013, Simple Machines
Joomla Bridge by JoomlaHacks.com
Valid XHTML 1.0! Valid CSS!
Page created in 0.061 seconds with 22 queries.
 
Exclusive Deal

sansfire13_245x90_cw90.jpg
SANSFIRE 2013
June 15 - 22

5% Off w/ Code: EHN_5

SANS Deals 4 EH-Netters
5% OFF Any SANS Course in Any Format!
Coupon Code: EHN_5 Including SANS Rocky Mountain 2013 & SANS Boston 2013
Polls
Compared to this year, 2013 will be:
 
Recent Forum Topics
EH-Net News Feeds
Latest Additions
 
         
Advertisement

© 2013 The Ethical Hacker Network
Joomla! is Free Software released under the GNU/GPL License.