Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-q6wc-xx4m-92fj
No affected components available
Impact
In version 1.20.0, when using new sync streams with config.edition: 3, certain subquery filters were ignored when determining which data to sync to users.
Depending on the sync stream configuration, this could result in authenticated users syncing data that should have been restricted.
Only queries that gate synchronization using subqueries without partitioning the result set are affected.
Not affected:
- Sync rules (bucket_definitions)
- Sync streams using
config.edition: 2 - No data is exposed without authenticating
Patches
The issue is fixed in 1.20.1. Restarting the service with the new version is sufficient - no reprocessing of sync streams is required.
Any data that users erroneously synced will be automatically removed from those devices when they connect again.
We have updated all affected PowerSync Cloud instances to the fixed version, and are reaching out to affected customers.
For self-hosted PowerSync instances, update to the latest version and restart.
Affected queries
Subqueries used only to determine whether or not a table should be synced (without partitioning the data itself) are affected. Examples:
-- Goal: Sync a table only to admin users
-- 1.20.0: all authenticated users would sync this table
SELECT * FROM sensitive_table WHERE auth.user_id() IN (SELECT user_id FROM admins)
SELECT * FROM sensitive_table WHERE 1 IN (SELECT 1 FROM users WHERE id = auth.user_id() AND is_admin = TRUE)
-- Goal: Sync a table only if authorized
-- 1.20.0: all authenticated users would sync this table
SELECT * FROM sensitive_table WHERE 'sensitive_table' IN (SELECT table_name FROM synced_table WHERE "user" = auth.user_id())
SELECT * FROM sensitive_table WHERE 'sensitive_table' IN auth.parameter('allowed_tables')
Queries that partition data (for example SELECT * FROM sensitive_table WHERE owner IN (SELECT id FROM users WHERE is_admin AND id = auth.user_id())) are not affected by this issue.
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker needs basic access or low-level privileges. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a high impact on the confidentiality of the information.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard