Vulnerability in supabase realtime

[ Description ]Official description

Supabase Realtime provides Broadcast, Presence, and Postgres Changes via WebSockets. Prior to version 2.103.1, the REST broadcast endpoints accept an expired JWT when the exp claim is encoded as a JSON string instead of a JSON number. The same route rejects an expired integer exp token signed with the same tenant secret. The accepted request returns 202 and emits the broadcast to subscribers. This could allow an unauthenticated attacker can broadcast realtime messages to subscribers. The attack can be performed via the Internet/only from within the supabase project. The impact of broadcasting messages to subscribers is application specific. This issue has been patched in version 2.103.1.

[ Fixes ]Fixes and patches

No fix or interim patch is linked from our sources yet. Check the vendor references below and limit exposure of affected systems until a fix is available.

[ References ]References

• github.com/supabase/realtime/commit/ac229d7eff2798b12b994e07bdd64f5e9b56374a
• github.com/supabase/realtime/pull/1934
• github.com/supabase/realtime/releases/tag/v2.103.1
• github.com/supabase/realtime/security/advisories/GHSA-hg9h-6mhq-6c2v