News for hackers. Stuff that matters.
Re:LastPass release fix for DOM manipulation vulnerability by tedunangst on Friday March 31, 2017 @10:07PM (#14009976)
Well, the controversy in this case is that Tavis announced the existence of a bug (no details). Not sure why that would upset anybody. You thought it was perfectly bugfree?
Re:LastPass release fix for DOM manipulation vulnerability by foota on Friday March 31, 2017 @10:17PM (#14010013)
It sounded like the parent was arguing for it not being wrong to do immediate full disclosure. I was responding to that. Perhaps the parent was merely talking about stating there is a vulnerability?

That is much more ethical. However, I am not sure that I believe it is something that would pass my threshold for clearly ethical (not your words, mine). You would need to weigh the damage to the company and consumer knee-jerk against the ability for consumers to make an informed decision about what they're willing to risk. In this case, maybe LastPass deserves for consumers to know immediately. They seem to have an extremely buggy program with a number of disclosed vulnerabilities. It's hard to know whether other programs are necessarily better though. Another factor that you should account for against disclosing is that stating the nature of the vuilnerability could potentially make it easier for someone to exploit. Do you think Tavis could find a vuln easier if I told him it was an RCE vs a CSRF bug? I do.

Re:LastPass release fix for DOM manipulation vulnerability by tedunangst on Friday March 31, 2017 @11:34PM (#14010255)
I suspect if you told tavis there was a RCE or CSRF bug, he would find one of each. I mean, I've found bugs by telling myself they existed. If I told myself it was a different bug, I'd find a different bug. Software is buggy.
Re:LastPass release fix for DOM manipulation vulnerability by geocar on Saturday April 01, 2017 @05:31AM (#14011351)
> Software is buggy.

This statement, while true, makes me sad.