Damn that's interesting. I like how they walked through step by step how they got the exploit to work. This is what actual real hacking is like, but much less glamorous than what you see in the movies.

I always wonder what's stopping security researchers from selling these exploits to Blackhat marketplaces, getting the money, waiting a bit, then telling the original company, so they end up patching it.

Probably break some contractual agreements, but if you're doing this as a career surely you'd know how to hide your identity properly.

Chances that such an old exploit get found at the same time by a whitehat and a blackhat are very small. It would be hard not to be suspicious.

Google, Apple, and rest of big tech are pregnable despite their access to vast amounts of capital, and labor resources.

I used to be a big supporter of using their "social sign on" (or more generally speaking, single sign on) as a federated authentication mechanism. They have access to brilliant engineers thus naively thought - "well these companies are well funded, and security focused. What could go wrong having them handle a critical entry point for services?”

Well as this position continues to age poorly, many fucking aspects can go wrong!

1. These authentication services owned by big tech are much more attractive to attack. Finding that one vulnerability in their massive attack vector is difficult but not impossible.
2. If you use big tech to authenticate to services, you are now subject to the vague terms of service of big tech. Oh you forgot to pay Google store bill because card on file expired? Now your Google account is locked out and now lose access to hundreds of services that have no direct relation to Google/Apple
3. Using third party auth mechanisms like Google often complicate the relationship between service provider and consumer. Support costs increase because when a 80 yr old forgot password or 2FA method to Google account. They will go to the service provider instead of Google to fix it. Then you spend inordinate amounts of time/resources trying to fix issue. These costs eventually passed on to customer in some form or another

Which is why my new position is for federated authentication protocols. Similar to how Lemmy and the fediverse work but for authentication and authorization.

Having your own IdP won’t fix the 3rd issue, but at least it will alleviate 1st and 2nd concerns

Yes, but I was saying the Blackhat marketplaces wouldn't really have much recourse if the person selling the exploit knew how to cover their tracks. i.e. they wouldn't have anyone to sue or go after.

Right, but when everyone got phone books, those were only shared locally in the town. It would be pretty hard to figure out someones phone number from across the state/country without the internet unless you knew someone in the town.

You could also pay to be unlisted, which is a luxury long since gone. How cool would it be to make your data 'unlisted' by paying a small monthly fee.

If you know how to hurt others, you can learn how to prevent that way of hurting others.

I always wonder what's stopping security researchers from selling these exploits to Blackhat marketplaces, getting the money, waiting a bit, then telling the original company, so they end up patching it.

Probably break some contractual agreements, but if you're doing this as a career surely you'd know how to hide your identity properly.

is that how guns work ?

is that how guns work ?

I think you missed the part at the very end of the page that showed the timeline of them reporting the vulnerability back in April, being rewarded for finding the vulnerability, the vulnerability being patched in May, and being allowed to publicize the vulnerability as of today.

Proton estimates the average Americans data is worth $700 per year.

Sign me up for $1000/year privacy fee and you will make more money by doing absolutely nothing.