2 ms·
Finding a vulnerability in a website and PoCing can be very much a crime. Finding a vulnerability in a product you own can also be constituted a crime under the
by dogma1138 9y ago
Finding a vulnerability in a website and PoCing can be very much a crime.
Finding a vulnerability in a product you own can also be constituted a crime under the DMCA or any other legislation that protects intellectual property and specifically prohibits reverse engineering.
The only difference is that companies elect not to file complaints which lead to charges being filed when this is done properly.
I've handled bug bounty payouts on both sides, I've sat on a advisory board for a national CERT (my employer held the seat not by name), and I've seen quite a few cases of bug bounty and reported submissions go wrong really fast for as something as silly as poorly constructed language or someone being overly pushy.
The OP here found a vulnerability that discloses PII of other users, if this is actual PII as defined by law in their jurisdiction well then they again just potentially commited a crime.
By the nature of the vulnerability "iterative exfiltriation of PII" I'm assuming they found some direct access to a resource like a profile page, invoices, or something similar which means that they've found a vulnerability, exploited it during a proof of concept and retrieved PII data, all of this falls under unauthorized and criminal access if not handled correctly.
Usually when you have a vulnerability which requires actionable exploitation to prove and you access any type of information especially one that is regulated by law you want to document everything you've accessed and provide those details in the disclosure as they would have to notify the people whose information has been exposed in the least if not their entire customer base.
- deleted 9y ago[deleted]