T09 · Insecure Skill Coding Practices
- Location
SKILL.md:31- Finding
Hardcoded Shared Supabase API Credential
- Content
View full analysis
Authorization: Bearer Content-Type: application/json ``` ``` ### Technical Analysis The skill embeds a long-lived Supabase anonymous API key and directs every installation to use it as both the `apikey` and bearer authorization credential. Although the key is explicitly described as publishable and carries the Supabase `anon` role, all users share the same project-level credential. It therefore provides no individual authentication or attribution and can be extracted without invoking the skill. Supabase publishable keys are expected to be exposed only when backend Row Level Security policies strictly constrain their capabilities. The repository does not contain those policies, so their effectiveness cannot be verified during this audit. Any overly broad database permission available to the `anon` role would be directly accessible to anyone possessing the embedded key. ### Attack Path 1. An attacker downloads or reads `SKILL.md`. 2. The attacker extracts the embedded JWT and Supabase REST endpoint. 3. The attacker supplies the JWT in the documented `apikey` and `Authorization` headers. 4. The attacker directly invokes endpoints exposed to the `anon` role without installing or using the skill. 5. If backend Row Level Security or endpoint authorization is incomplete, the attacker reads or modifies accessible records, submits unauthorized content, consumes service quo ...[truncated 824 chars]- Remediation
View remediation
