Re:Thousands of Apps Leak Sensitive Data via Misconfigured F...
by ProblemFactory on Friday June 29, 2018 @10:51AM
(#17424837)
Firebase Database default settings make the entire database world-readable and world-writable by all "authenticated users". But once you have enabled authentication, then that means anyone who signs into your app with a Google account. Restricting users to only access their own data requires understanding and writing "security rules".
It's the most irresponsible default I have seen in practice.
Re:Thousands of Apps Leak Sensitive Data via Misconfigured F...
by z5h on Friday June 29, 2018 @10:56AM
(#17424869)
I disagree. I bet if the default was no access, developers would simply enable all access (and not even realize they could restrict access to authenticated users).
So the default is likely much safer than what would otherwise happen.
Let's not forget that there is a security/permissions testing feature built right into Firebase. It would literally take 1 minute for a dev to ask and test: hey, can people read each other's data?
Re:Thousands of Apps Leak Sensitive Data via Misconfigured F...
by rhizome on Friday June 29, 2018 @11:59AM
(#17425234)
developers would simply enable all access (and not even realize they could restrict access to authenticated users). So the default is likely much safer than what would otherwise happen.
That's not what "safer" means. You cannot say that that's what would happen, either.
Re:Thousands of Apps Leak Sensitive Data via Misconfigured F...
by maxxxxx on Friday June 29, 2018 @11:07AM
(#17424936)
We are using a system called Kinvey and there it's the same . By default everyone can read everybody's data. You can restrict it but I don't understand why they don't have a restricted model as default.
Was the mistake in the default Firebase configuration settings, or were common poor choices made by each of the app developers independently?