Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to version 4.10.4, for regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the `Parse.User` class, all session tokens created during user sign-ups will be broadcast as part of the LiveQuery payload. A patch in version 4.10.4 removes session tokens from the LiveQuery payload. As a workaround, set `user.acl(new Parse.ACL())` in a beforeSave trigger to make the user private already on sign-up.
References
Link | Resource |
---|---|
https://github.com/parse-community/parse-server/commit/4ac4b7f71002ed4fbedbb901db1f6ed1e9ac5559 | Patch Third Party Advisory |
https://github.com/parse-community/parse-server/releases/tag/4.10.4 | Release Notes Third Party Advisory |
https://github.com/parse-community/parse-server/security/advisories/GHSA-7pr3-p5fm-8r9x | Mitigation Third Party Advisory |
Configurations
History
No history.
Information
Published : 2021-09-30 15:15
Updated : 2024-02-28 18:48
NVD link : CVE-2021-41109
Mitre link : CVE-2021-41109
CVE.ORG link : CVE-2021-41109
JSON object : View
Products Affected
parseplatform
- parse-server
CWE
CWE-200
Exposure of Sensitive Information to an Unauthorized Actor