<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"><channel><title>Matasano Chargen - Latest Comments in Vulnerability Reporting in a Web 2.0 World</title><link>http://matasanochargen.disqus.com/</link><description></description><language>en</language><lastBuildDate>Fri, 01 Jun 2007 20:00:04 -0000</lastBuildDate><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322703</link><description>Try contacting their funding source or, better yet, their lawyers. These days, those folks understand the words "risk to brand", etc.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Money and lawyers</dc:creator><pubDate>Fri, 01 Jun 2007 20:00:04 -0000</pubDate></item><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322702</link><description>stacy:&lt;br&gt;&lt;br&gt;In this situation, I dont think the cost of one customer is going to motivate anyone.  Besides, not using products and services everytime there is a security issue that isn't resolved to my satisfaction would basically cause me to stop using computers. :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave G.</dc:creator><pubDate>Thu, 31 May 2007 11:04:38 -0000</pubDate></item><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322701</link><description>So maybe you should "vote with your wallet" and look for an alternative application.&lt;br&gt;&lt;br&gt;If you don't consider the vulnerability serious enough to not use the application, why should they think it is serious enough to expend resources to fix?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">stacy</dc:creator><pubDate>Mon, 28 May 2007 13:11:48 -0000</pubDate></item><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322700</link><description>Picking functionality over security there, Tom? ;)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ryan Russell</dc:creator><pubDate>Sun, 27 May 2007 04:03:09 -0000</pubDate></item><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322699</link><description>They could get vindictive and kick us off their application! No thanks!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas Ptacek</dc:creator><pubDate>Fri, 25 May 2007 18:47:29 -0000</pubDate></item><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322698</link><description>Those of us who tend a little more towards the punitive end of the spectrum would tend to say that at this point, you name the company (if not the vuln.)&lt;br&gt;&lt;br&gt;Yay! Free education for everybody...&lt;br&gt;&lt;br&gt;(Or perhaps in your subtlety, you're going to point them at this entry and ask nicely one more time... if so, where's the hash of your advisory?)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ryan Russell</dc:creator><pubDate>Fri, 25 May 2007 12:58:16 -0000</pubDate></item><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322697</link><description>I think some Web 2.0 companies have not transitioned internally from being short-sighted to longer-sighted. In the short term, unless you're actually selling security, the impetus is to get the product viable and functional. Security just can't be a cost or detractor from that. Longer-term, devels can start thinking about security and doing things the right way, once a little bit more of their future is "secured." (Pun intended!)&lt;br&gt;&lt;br&gt;Others just like to build things...maintenance (and beefing up security) are sometimes not what they want to do. :\&lt;br&gt;&lt;br&gt;Not saying that's right, but...damnit... :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">LonerVamp</dc:creator><pubDate>Fri, 25 May 2007 11:20:11 -0000</pubDate></item><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322696</link><description>secure software contracts annexes based on owasp/mitre/wasc/samate/sans-ssi (probably in that order) certifications are the future of web 2.0 b2b.&lt;br&gt;&lt;br&gt;unfortunately, only sans-ssi exists right now, although owasp has this:&lt;br&gt;&lt;a href="http://www.owasp.org/index.php/OWASP_Secure_Software_Contract_Annex" rel="nofollow"&gt;http://www.owasp.org/index.php/OWASP_Secure_Sof...&lt;/a&gt;&lt;br&gt;and mark curphey got like $200k to work on a project called "owasp ceritification" a few weeks ago which he claims will replace pci.  pci-dss and texas are going to hell in a handbasket as they well should.&lt;br&gt;&lt;br&gt;i talked about this at chisec last night</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">dre</dc:creator><pubDate>Fri, 25 May 2007 11:05:54 -0000</pubDate></item><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322695</link><description>This company didn't treat the vuln report as a bug. They treated it as a FEATURE REQUEST.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Thomas Ptacek</dc:creator><pubDate>Fri, 25 May 2007 10:34:23 -0000</pubDate></item><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322694</link><description>Unlike software companies, I'm really paranoid about reporting vulnerabilities to websites. The best you can reasonably hope for is that they won't try to sue. :(&lt;br&gt;&lt;br&gt;This is maybe about where software companies were 15 or 20 years ago.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dan Weber</dc:creator><pubDate>Fri, 25 May 2007 10:30:46 -0000</pubDate></item><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322693</link><description>I notified a website back in October that they had multiple serious security flaws. Including some really stupid ones -- among them, "authentication" resulted in you getting a cookie set to your username -- change the cookie, become another user.&lt;br&gt;&lt;br&gt;Their response was along the lines of "oops, yeah, we should totally fix that!".  I followed up two months later, never heard back and forgot about it until now.  Checked again, and they're still vulnerable. &lt;br&gt;&lt;br&gt;*sigh*</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jordan Wiens</dc:creator><pubDate>Fri, 25 May 2007 10:12:29 -0000</pubDate></item><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322692</link><description>At least they didn't take you to court... yet. ;-)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">magnus</dc:creator><pubDate>Fri, 25 May 2007 10:06:57 -0000</pubDate></item><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322691</link><description>What we need is disclosure 2.0 guidelines for web 2.0 software. Dave did the right thing by informing the software company.  The software company did the wrong thing by treating this as a bug.  Perhaps there should be a "hall of web 2.0 shame" for companies that don't fix vulnerabilities reported to them in a timely way.&lt;br&gt;&lt;br&gt;Perhaps we need a place where researchers like Dave can submit a posting saying they have informed Vendor X of Vulnerability Y on Date Z with CVSS score of A.  Then Vendor X can get this taken off the list by saying they fixed it.  If it wasn't really fixed Dave can inform the list and it goes back on.  Use web 2.0 to police web 2.0.&lt;br&gt;&lt;br&gt;-Chris</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">chrisw</dc:creator><pubDate>Fri, 25 May 2007 09:49:26 -0000</pubDate></item><item><title>Re: Vulnerability Reporting in a Web 2.0 World</title><link>http://www.matasano.com/log/866/vulnerability-reporting-in-a-web-20-world/#comment-2322690</link><description>Web 2.0 + Security was like DotCom + Logic, they aren't mean't to be :)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Daniel</dc:creator><pubDate>Fri, 25 May 2007 04:04:02 -0000</pubDate></item></channel></rss>