Capgo (capgo.app) is affected by an authorization flaw in the app icon update path

Why it is Yellow

• CVSS 8.5 high

References

• https://github.com/Cap-go/capgo.app/security/advisories/GHSA-669c-gwrr-hc53
• https://www.vulncheck.com/advisories/capgo-app-icon-update-privilege-escalation-via-service-role-worker
• https://github.com/Cap-go/capgo.app/security/advisories/GHSA-669c-gwrr-hc53

Original description

Capgo (capgo.app) is affected by an authorization flaw in the app icon update path. The PUT /app/:id endpoint accepts a user-controlled `icon` value, normalizes it, and stores it in public.apps.icon_url without verifying that the image path belongs to the target app's own image namespace (e.g. org/{owner_org}/{app_id}/...). Updating apps.icon_url fires the on_app_update trigger, whose worker reads record.icon_url and calls cleanStoredImageMetadata(), which runs with service-role credentials (supabaseAdmin()) and downloads and re-uploads the referenced storage object with upsert: true. As a result, an authenticated holder of an app-limited write API key can cause the privileged worker to rewrite an out-of-scope private image object (for example an organization logo) that the key cannot read or write directly under Supabase Storage RLS. All versions are affected; no patched version was available at the time of the advisory.