Skip to content

🔒 Restrict read access to authenticated users for configs_prod - #96

Open
eng618 wants to merge 2 commits into
mainfrom
security-fix-firestore-rules-configs-prod-3791365302711408600
Open

🔒 Restrict read access to authenticated users for configs_prod#96
eng618 wants to merge 2 commits into
mainfrom
security-fix-firestore-rules-configs-prod-3791365302711408600

Conversation

@eng618

@eng618 eng618 commented Aug 5, 2026

Copy link
Copy Markdown
Owner

🎯 What:

Fixed an overly permissive Firestore read access vulnerability on the production configurations (configs_prod) collection in apps/parable-bloom/firestore.rules.

⚠️ Risk:

Allowing public read access (allow read: if true;) to the production configuration collection permits unauthorized external entities/anonymous users to read potentially sensitive system configuration details, schemas, modules registry, OTA update metadata, and logical level mappings. This could expose system architectural details and facilitate targeted attacks or reverse engineering of the application's config schema.

🛡️ Solution:

Tightened read permissions in the match /configs_prod/{configId} block in Firestore security rules to only allow authenticated requests (allow read: if request.auth != null;). This ensures that only verified users signed in through Firebase Auth can retrieve the production app configuration details, minimizing the exposure surface while preserving standard user gameplay capability.


PR created automatically by Jules for task 3791365302711408600 started by @eng618

Co-authored-by: eng618 <3827863+eng618@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@codacy-production

codacy-production Bot commented Aug 5, 2026

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

…rsing

Co-authored-by: eng618 <3827863+eng618@users.noreply.github.com>
@github-actions

github-actions Bot commented Aug 5, 2026

Copy link
Copy Markdown
Contributor

🚀 Preview Deployed!

Your changes are now live for testing:

🌐 Preview URL: https://parable-bloom--pr-96-bqjo7rl6.web.app

This preview will be automatically cleaned up when the PR is closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant