First published: Thu Sep 30 2021(Updated: )
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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Parseplatform Parse-server | <4.10.4 |
https://github.com/parse-community/parse-server/commit/4ac4b7f71002ed4fbedbb901db1f6ed1e9ac5559
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-41109 is a vulnerability in Parse Server, an open-source backend for Node.js, where the session token is not removed from LiveQuery payloads, potentially exposing user data.
The severity of CVE-2021-41109 is rated as high with a CVSS score of 7.5.
CVE-2021-41109 affects Parse Server versions up to and excluding 4.10.4 by not removing the session token from LiveQuery payloads, which could lead to unauthorized access to user data.
To fix CVE-2021-41109, you should update Parse Server to version 4.10.4 or newer, as this release addresses the vulnerability by removing the session token from LiveQuery payloads.
Yes, you can find more information about CVE-2021-41109 in the following references: [GitHub Commit](https://github.com/parse-community/parse-server/commit/4ac4b7f71002ed4fbedbb901db1f6ed1e9ac5559), [Release Notes](https://github.com/parse-community/parse-server/releases/tag/4.10.4), [Security Advisory](https://github.com/parse-community/parse-server/security/advisories/GHSA-7pr3-p5fm-8r9x).