Re:CircleCI trusts 8 analytics companies with your source co...
by kevinburke on Tuesday October 10, 2017 @10:37PM
(#15446912)
That would have been appropriate if I had found e.g. an endpoint that did not accept CSRF tokens, or a vulnerability in Ring. It's not appropriate when the problem is they made a business decision to expose my source code to Quora.js.
Re:CircleCI trusts 8 analytics companies with your source co...
by otterley on Wednesday October 11, 2017 @12:34AM
(#15447306)
How do you know it was a conscious decision, as opposed to ordinary human oversight? As the old saying goes, never ascribe to malice what can be adequately ascribed to incompetence. (Though I wouldn't go so far as to call CircleCI "incompetent" -- security issues are rampant in this industry, despite everyone's best efforts.)
Re:CircleCI trusts 8 analytics companies with your source co...
by rapind on Wednesday October 11, 2017 @03:01AM
(#15447778)
I'd say it's more of a tossup. I mean they write software for people who write software.
I think we can rule out a malicious decision regardless though. I'd wager if it was flagged by the annoyingly pedantic but super smart developer, then it's still sitting in their Trello board buried under a few hundred features that were considered a higher priority by the product manager. In this case, the decision felt mostly harmless.
Or yeah, probably just as likely that no one noticed.
Also, it's not swept under the carpet - it ends up usually getting $ for the reporter and a better story as they'd also know how the company fixed it. If they refuse to fix, then publish away.
https://en.wikipedia.org/wiki/Responsible_disclosure