AI & Agent Dev Bug Sandbox Back to Radar

Storage Policy Bucket Misattribution For Multi-Bucket And Negated Conditions

The Studio storage policy parser incorrectly attributes bucket-scoped policies, causing multi-bucket policies to appear under only one bucket and negated policies to appear under excluded buckets. This can mislead audit and lead to deletion of policies that still protect other buckets.

highConfidence 87%React Affected Vmaster

Origin Analysis

`extractBucketNameFromDefinition` in `apps/studio/components/interfaces/Storage/Storage.utils.ts` splits policy definition on ' AND ', selects the first segment containing `bucket_id`, and returns the first quoted string. It does not handle `IN` lists, `ANY (ARRAY[...])`, `<>`/`!=` negation, or multiple buckets, so it always returns one bucket and ignores operator semantics.

1. Create two buckets `avatars` and `logos`. 2. Run SQL: `create policy "Multi bucket read" on storage.objects for select to authenticated using (bucket_id in ('avatars','logos'));` 3. Open Storage > Policies; policy only shows under `avatars`, not `logos`. 4. Run `create policy "Not avatars" on storage.objects for select using (bucket_id <> 'avatars');` and observe it appears under `avatars`; deleting `avatars` deletes it.

Fixing Code Block

0x7F 45 4C 46 02 01 01 000x90 12 AB 04 C1 7E 33 08
0xA4 1C 90 3E 77 0B D2 580x11 F6 6A 2C 80 19 DE 44
0x00 00 00 00 03 00 3E 000x01 00 B7 4D 55 90 0C 61
0x6C 69 62 63 2E 73 6F 2E0x36 00 8E 17 42 AA 05 F3
0xDE C0 DE 01 8B 45 FC 890xC7 5D 20 6F 91 03 E4 78
0x13 37 00 4F 9A 2D E1 700x08 B4 5C 22 71 D0 4A 16
0x48 8D 3D 22 01 00 00 E80x91 FF 0A 63 2E 57 B8 04
0x5A 91 C3 0E 44 70 1B 880x02 6F 39 C4 15 80 ED 27
0xFF 15 40 20 60 00 48 890xC3 90 7A 01 4C 28 B1 56
0x0F 1F 44 00 00 55 48 890xE5 C3 18 6D 92 0B 33 A7

Edge Case Audit

Changing the function signature will break current call sites unless updated. Ensure all three consumers (Policies page, useBucketPolicyCount, DeleteBucketModal) are migrated simultaneously. On rollback, re-deploy previous parser but the bug persists. Test with multi-bucket, negated, and ANY array policies. Be cautious with policies created by older Studio versions or manually crafted SQL that may not match regex (e.g. complex expressions with OR); consider fallback to full definition scan if regex misses.