Parse Server: Protected Fields Can Be Inferred by Attackers

Summary

An attacker can learn sensitive information about your Parse Server data by using a special feature called LiveQuery. This is a concern if your server has protected fields and LiveQuery enabled. To fix this, update your Parse Server to the latest version or temporarily disable LiveQuery for affected classes.

What to do

Update parse-server to version 9.6.0-alpha.9.
Update parse-server to version 8.6.35.

Affected software

Vendor	Product	Affected versions	Fix available
–	parse-server	> 9.0.0 , <= 9.6.0-alpha.9	9.6.0-alpha.9
–	parse-server	<= 8.6.35	8.6.35
parseplatform	parse-server	<= 8.6.35	–
parseplatform	parse-server	> 9.0.0 , <= 9.6.0	–
parseplatform	parse-server	9.6.0	–
parseplatform	parse-server	9.6.0	–
parseplatform	parse-server	9.6.0	–
parseplatform	parse-server	9.6.0	–
parseplatform	parse-server	9.6.0	–
parseplatform	parse-server	9.6.0	–
parseplatform	parse-server	9.6.0	–
parseplatform	parse-server	9.6.0	–

Original title

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.9 and 8.6.35, an attacker can exploit LiveQuery subscriptions to infer t...

Original description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.9 and 8.6.35, an attacker can exploit LiveQuery subscriptions to infer the values of protected fields without directly receiving them. By subscribing with a WHERE clause that references a protected field (including via dot-notation or $regex), the attacker can observe whether LiveQuery events are delivered for matching objects. This creates a boolean oracle that leaks protected field values. The attack affects any class that has both protectedFields configured in Class-Level Permissions and LiveQuery enabled. This vulnerability is fixed in 9.6.0-alpha.9 and 8.6.35.

nvd CVSS4.0 6.9

Vulnerability type

CWE-200 Information Exposure