Parse Server vulnerable to brute force guessing of user sensitive data via search patterns
High severity
GitHub Reviewed
Published
Sep 2, 2022
in
parse-community/parse-server
•
Updated Jan 30, 2023
Package
Affected versions
< 4.10.14
>= 5.0.0, < 5.2.5
Patched versions
4.10.14
5.2.5
Description
Published by the National Vulnerability Database
Sep 7, 2022
Published to the GitHub Advisory Database
Sep 16, 2022
Reviewed
Sep 16, 2022
Last updated
Jan 30, 2023
Impact
Internal fields (keys used internally by Parse Server, prefixed by
_
) and protected fields (user defined) can be used as query constraints. Internal and protected fields are removed by Parse Server from query results and are only returned to the client using a valid master key. However, using query constraints, these fields can be guessed by enumerating until Parse Server returns a response object.Patches
The patch requires the master key to use internal and protected fields as query constraints.
Workarounds
Implement a Parse Cloud Trigger
beforeFind
and manually remove the query constraints, such as:References
References