I wouldn't blame Twilio. It's entirely Parler's fault they allowed an unvalidated account to successfully register and log in.
Of course, it's also entirely the intruder's fault they exploited the wide open security hole.
Either way, this feels like something that will end in a lawsuit.
---
With regards to reports of cyber security issues Parler experienced and have been attributed to Twilio, our security team investigated the claims and found no evidence indicating their security issues were related to Twilio or our products. Per our Website [0], Twilio has not issued any press releases pertaining to or referencing Parler.
Furthermore, Parler was using Twilio to send out identity verification codes for new downloads or password resets. Once a user was verified, security protocols were independently handled by Parler and did not involve Twilio or its products. On Friday, January 8th, we sent Parler a letter informing them they were in violation of our Acceptable Use Policy [1] and notifying them that we would suspend their account if they did not make efforts to remediate multiple calls for violence on their platform. Shortly after receiving our letter, Parler informed us they had already turned off their integration with Twilio.
Any cyber security issues experienced by Parler were completely unrelated to Twilio or any of its products.
I know that not all press statements are going to be on the website.
From the perspective of any company using a service like twilio (i.e., not just Parler and this specific set of events), would there not be some sort of failsafe in case something just like this were to happen? Or would this kind of thing be so nearly inconceivable that you wouldn't protect against it?
* Fail and essentially have downtime on the features using the API
* Succeed and essentially have no authentication for that time but no downtime
Parler took the second approach. Platforms that value security would take the first approach.
Can someone explain what does this mean?
I guess you could imagine user accounts being created with `authenticated=null`, and then having `authenticated=False|True` set in the in the success handler for some Twillio API call. Having null as the default would allow you to see in the database where authentication emails hadn't been sent out, so you could resend them.
And then I guess you could imagine a developer checking authentication by looking for cases where `!authenticated`, rather than `authenticated == True`. Granted I don't think this hack is real, but if it were then that's probably how it would play out.
It seems to involve some skipped auth steps on someones part though, not just a fail-safe/fail-dead mixup. It's not clear.
Instead of having "if explicitly ok, proceed", they maybe had "unless it's an explicit negative response in an expected format (or a connectivity issue, timeout, etc.), proceed"?
Which would be a pretty dumb thing to do, but I've seen worse.
That would be a very unsafe default.
I tried to create an account on Parler last night to check which services were turned off by AWS. I entered dummy data into their form. The POST to their auth service timed out...but the auth flow took you to the success page anyway?
That seems to be the consensus.
If any of these Twitter or Reddit posts are true then I would talk to a lawyer before participating.
The team at archive.org is importing the full archive right now.
Twilio as a B2B doesn't gain a lot from being a "woke" company and following the trend of lynching Parler, on the contrary this can and will scream how Twilio can put your whole platform down overnight..
I wonder when are we going to see a legal discussion if / when internet access is going to become a basic human right? Just like electricity became ubiquitous, I expect internet access (email, payment processing, etc) to also become a right.
Is electricity a right?
They can't cut a customer's power over his politics--especially paying customers!
It is reasonable to suggest that Internet bandwidth should be a public utility.
If you consider an internet connection a public utility, which we should, then that would be ostracism. In terms of companies being able to successfully run their businesses, are we at the point where a "cloud provider" should be considered part of a country's infrastructure?
I can agree with the point being made about an internet connection, but Parler was still able to buy some servers and self-host. Unless there's an argument here to consider cloud providers a de-facto component of a nation's tech infrastructure. Seeing as we have no proper public regulation of the sector and no public player providing the service, I'm not sure how far that argument would go. It's still an interesting question to ponder on, I guess.
Well, because of that access, it gave them access to the behind the login box API that is used to deliver content -- ALL CONTENT (parleys, video, images, user profiles, user information, etc) --. But what it also did was revealed which USERS had "Administration" rights, "Moderation" rights.
Well, then what happened, those user accounts that had Administration rights to the entire platform... The hackers, internet warriors, call it what you will, was able to use the forgot password link to change the password. Why? Because Twilio was no longer authenticating emails. This meant, they'd get directly to the reset password screen of that Administration user."
I'm not from the US, but as an outsider, this leaves a really bad taste with how Twilio handled the situation AS A BUSINESS.