4 ms·
"Responsible disclosure" is an invention of vendors who want you conforming to their policies and timelines (and more). Tesla is also "good" at disabling aspec
by FireBeyond 7y ago
"Responsible disclosure" is an invention of vendors who want you conforming to their policies and timelines (and more).
Tesla is also "good" at disabling aspects of people's property (like ethernet ports, or ability to receive future firmware updates) when they dislike what people find "wrong" or otherwise in Tesla software.
- zamadatix 7y agoYou're always welcome to disclose to the company and follow your own timelines and policies. Presumably this doesn't change whether you tell the company first or post it on your GitHub. Shitty either way but irrelevant.
- corndoge 7y agoYou can do responsible disclosure without following a vendor's timeline. Project Zero comes to mind. It's not like the only options are either dropping 0 days or doing exactly as the vendor says. Simply give a date. At the end of the day the point of security research is to make things more secure. Oftentimes that is best achieved by working with the vendor.
- kortilla 7y ago> "Responsible disclosure" is an invention of vendors who want you conforming to their policies and timeline No it’s not. It’s an invention of ethical hackers and academic security researchers who are mature enough to realize that dropping 0-days to the public is worse for society than giving the vendor a reasonable opportunity to fix it. “Economics of information security” is a field that publishes some studies about vulnerability disclosure strategies and maximizing the social good.
- FireBeyond 7y agoSome interesting commentary: https://news.ycombinator.com/item?id=14010010 https://news.ycombinator.com/item?id=14010010 https://news.ycombinator.com/item?id=12308246 https://news.ycombinator.com/item?id=12308246 > That may feel good to say, but as someone whose job it was to find these kinds of bugs in software from companies ranging from tiny startups to financial exchanges to major tech vendors, this is a kind of carelessness shared by virtually everyone shipping any kind of software anywhere. > That said, the term "responsible disclosure" is Orwellian, and you should very much avoid using it. > It's coercive. It redefines language to make any handling of vulnerabilities not condoned by the vendors who shipped those vulnerabilities "irresponsible", despite the fact that third parties who discover vulnerabilities have no formal duty to cooperate with those vendors whatsoever. > The better term is "coordinated disclosure". But uncoordinated disclosure is not intrinsically irresponsible. For instance: if you know there's an exploit in the wild for something, perhaps go ahead and tweet the vulnerability without notice!
- wahern 7y ago> That said, the term "responsible disclosure" is Orwellian, and you should very much avoid using it. It seems you disapprove of the phrase "responsible disclosure" because it's ambiguous and can be used as a cudgel. That's no different than the term "Orwellian", which is ambiguous and can be used as a cudgel. All people are saying is that it's better to give the vendor a heads up before releasing an exploit. Maybe they have something to tell you that might cause you to delay; maybe not. Surely responsible disclosure implies to most people some amount of due diligence in choosing a timeline for disclosure. If you don't give a vendor any opportunity to discuss, there's been no such due diligence on your part.
- ryanlol 7y ago>It seems you disapprove of the phrase "responsible disclosure" because it's ambiguous and can be used as a cudgel This is like saying that a glock can be used as a weapon. Yes, it was carefully designed to be one. >We must secure the existence of our people and a future for white children This might also be ambiguous, but we all understand the genocidal connotations.
- cyphar 7y ago> This might also be ambiguous, but we all understand the genocidal connotations. Ah yes, because using the term "responsible disclosure" is very clearly analogous to being a white supremacist. There's no need to be so ridiculously dramatic -- "responsible disclosure" was objectively the term-du-jour used by the infosec community until fairly recently. And it's perfectly understandable why the community changed their mind (vendors started co-opting the phrase as a method of shaming researchers for doing the right thing), but you are shooting yourself in the foot by being so aggressive about it. Why not just say "we used to use that term, but we use this other term now because of the following reasons"?
- ryanlol 7y agoYou've got the order of events wrong here. The term "responsible disclosure" originated from the legal teams of vendors around 2002, it was never co-opted by vendors. Here's a little historical context https://www.securityfocus.com/columnists/120 https://www.securityfocus.com/columnists/120 I think the 14 words comparison is apt. Without context there's nothing obviously wrong with the 14 words, just like there's nothing obviously wrong with "responsible disclosure".
- kerng 7y agoI think this comment highlights a lack of understanding what responsible disclosure is about. It's there to reach the best possible tradeoffs to protect consumers and force a quick turnaround with fixes. Just publishing vulns, which the vendor might not even see or learn about(!), will not help in getting things improved and puts consumers knowingly at risk at scale.
- FireBeyond 7y agoI understand perfectly well what it is. But see my sibling comments, that reflect an agreement with the concept of "coordinated disclosure", rather than "responsible disclosure", which gives an implication that I am being irresponsible if I do not work to the vendor's needs and priorities.
- ryanlol 7y agoPerhaps you should come up with your own term to describe such disclosures instead of co-opting the well established one that means something else entirely?
- cyphar 7y agoI have followed this shift in vocabulary -- now the term for not dropping a 0day is "coordinated disclosure" and usually implies that the researcher has final say on the disclosure timeline. But what I don't understand is why so many folks in infosec pretend as though "responsible disclosure" has always been a dirty word -- from memory, it was the primary term used by the infosec community until only a few years ago.
- mlindner 7y ago> "Responsible disclosure" is an invention of vendors who want you conforming to their policies and timelines (and more). Ridiculous. Please don't put out this kind of nonsense. Responsible disclosure is to protect the users of software. Supply chains cannot and do not respond instantaneously. You cannot fix a security problem within microseconds. There MUST be some delay between disclosure to the software provider and the actual release. Otherwise you're just endangering the public. How much delay is certainly a point of discussion, but no one is saying "no delay".