fix(db): harden transfer_app against app id enumeration

[riderx]

Summary (AI generated)

• Removed anonymous access to public.transfer_app via REVOKE ALL ... FROM anon in a new migration.
• Updated transfer_app to return a uniform error message for non-existent apps and unauthorized requests when called without valid user context.
• Kept transfer permission checks and cooldown logic intact while adding explicit unauthenticated call logging.
• Ran SQL lint on the updated migration file to satisfy repo formatting and SQL style checks.

Motivation (AI generated)

transfer_app was previously callable by the anonymous/publiable role, allowing unauthenticated callers to infer valid app_id values from distinct error payloads. This is a confidentiality/tenant-enumeration risk.

Business Impact (AI generated)

• Prevents anonymous app-identifier enumeration that can aid targeted abuse or reconnaissance.
• Preserves existing transfer safeguards while reducing information disclosure risk.
• Keeps behavior for authenticated workflows unchanged where applicable.

Test Plan (AI generated)

• bunx sqlfluff lint --dialect postgres supabase/migrations/20260224120000_fix_transfer_app_security.sql
• Deploy migration to a staging Supabase instance and confirm anon rest/v1/rpc/transfer_app requests cannot transfer or enumerate app IDs.
• Confirm authenticated transfer path still functions for authorized users with valid app/org permissions.

Generated with AI

[coderabbitai]

Warning

Rate limit exceeded

@riderx has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 11 minutes and 54 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 5cb5da2 and 9a414d1.

📒 Files selected for processing (1)

• supabase/migrations/20260224120000_fix_transfer_app_security.sql

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch riderx/fix-transfer-enum

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bc784596f8

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Revoke transfer_app from PUBLIC to block anonymous execution

This migration only revokes transfer_app from anon, but PostgreSQL function privileges are also inherited from the PUBLIC pseudo-role; because this function was historically granted without a preceding REVOKE ... FROM PUBLIC (see existing grants in 20250530233128_base.sql), anonymous callers can still execute it via PUBLIC, so the intended RPC hardening is ineffective in production-like databases.

Useful? React with 👍 / 👎.

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud