TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

The Firestore vulnerability found in Arc is likely widespread

42 pointsby venkii8 months ago

4 comments

smallerfish8 months ago
I bet supabase also have a lot of naive users who haven&#x27;t enabled RLS in their postgres instances (last I checked, not enabled by default), but are nevertheless sharing api keys client side in their apps (<a href="https:&#x2F;&#x2F;supabase.com&#x2F;docs&#x2F;reference&#x2F;javascript&#x2F;initializing">https:&#x2F;&#x2F;supabase.com&#x2F;docs&#x2F;reference&#x2F;javascript&#x2F;initializing</a>).<p>Supabase support&#x27;s defense is &quot;well, if you read the manual you&#x27;ll understand how to set this up properly&quot;, but that&#x27;s not how bootcamp developers tend to work.<p>I spent 10 minutes seeing if I could convince google or kagi to search for sites like these, but unfortunately js isn&#x27;t searchable in either.
评论 #41629242 未加载
评论 #41630099 未加载
spankalee8 months ago
Firestore is great, especially as a cleaned up and more capable version of Datastore, but Firebases&#x27;s influence on it as a successor to Firebase Realtime DB is showing in this complexity here.<p>IMO, the easiest and most secure thing is to not do direct DB reads and writes from your client. Use a traditional client-server architecture and have your server talk to the DB.<p>The times I do use the Firestore client library, it&#x27;s only for reading and only for the realtime updates. My security rules disallow all writes.
acheong088 months ago
I’ve used Firestore a few years back. Just checked and indeed the same vulnerability is present. Users can’t create&#x2F;change submissions with a different userID but can change the userID of their own submissions, thus impersonating someone else.<p>Of course, that was 2021 and I had barely started programming. Not sure if I’d make the same mistake now (of using Firestore in the first place :)
stevebmark8 months ago
What is the intent of allowing arbitrary document assignment to any other global user in the system, with zero default security checks in place? That seems like a fundamentally terrible idea. Other sharing systems require explicit steps to share documents between users (sharing a Google doc with an email address, for example), and it&#x27;s a very controlled workflow. In Firestore, user IDs are global, and you can arbitrarily give them data? Even if you can get around this with specific security rules, why is this even a thing in the first place?
评论 #41629323 未加载