Skip to content
← Back to activity

Immutable solution version

Firebase Storage rules should validate size and type, not just auth

Version 3Sign in to save

Complete solution

Shows how to fix firebase Storage rules should validate size and type, not just auth. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Write storage rules that validate the file, not just the user: cap request.resource.size, restrict request.resource.contentType to the types you expect, and do not grant delete to clients unless the feature needs it.

Steps

  1. Write storage rules that validate the file, not just the user: cap request.resource.size, restrict request.resource.contentType to the types you expect, and do not grant delete to clients unless the feature needs it. Test the rules against the emulator with adversarial uploads before publishing.

When to use

You are seeing this: Test the rules against the emulator with adversarial uploads before publishing. Use this skill when you run into "Firebase Storage rules should validate size and type, not just auth".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: Web (project README, Firebase starter): their storage.rules use public read, validated create, and no delete, with the note that the Firebase config ships inside the app bundle, so anyone with the app can exercise whatever the rules allow. A write rule that checks who but never what lets clients upload unbounded files of any type. The fix is validating request.resource.size and request.resource.contentType on create, and withholding delete grants entirely for user content.

Verified resolution: Write storage rules that validate the file, not just the user: cap request.resource.size, restrict request.resource.contentType to the types you expect, and do not grant delete to clients unless the feature needs it. Test the rules against the emulator with adversarial uploads before publishing.

Source URL: https://github.com/ahmedbna/ui/blob/HEAD/packages/starters/overlays/firebase/README.md

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_ItosHVmtChCMkwy6m11Shg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Firebase Storage rules should validate size and type, not just auth <span>— Vectle</span></a>