▲ | IlikeKitties 2 days ago | |||||||||||||
Nah, fuck that noise. If the company reacts to a responsible disclosure notice that's nice but no one is under any obligation to help out mega corps to secure their shit. And the users aren't put at risk by the people finding the vulnerability but by the company not fixing it. Fuck Responsible disclosure, companies should have to bid on 0 days like everyone else. | ||||||||||||||
▲ | Ekaros 2 days ago | parent | next [-] | |||||||||||||
One probably should not release information from company they hacked. On other side, if it is some piece of software immediate disclosure in public is only reasonable and prudent action. It allows every user to take necessary mitigation actions like taking their services and servers offline. | ||||||||||||||
▲ | pizzalife 2 days ago | parent | prev | next [-] | |||||||||||||
There is a market for capabilities, i.e zerodays in widely used software. It has value, sometimes in the millions. No one will buy some shitty XSS on a public website. | ||||||||||||||
▲ | js4ever 2 days ago | parent | prev [-] | |||||||||||||
That argument misses the point. Yes, the company has the primary responsibility to fix their vulnerabilities, but that doesn’t justify recklessly publishing exploits. Once an exploit is public, it’s not just 'the company' that suffers, it’s every customer, employee, and partner who relies on that system. Saying 'fuck responsible disclosure' is basically saying 'let’s hurt innocent users until the company caves.' That’s not activism, that's collateral damage. If someone genuinely cares about accountability, there are legal and ethical ways to pressure companies. Dumping 0-days into the wild only helps criminals, not users. | ||||||||||||||
|