CVE-2021-41109

moderate-risk
Published 2021-09-30

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.

Do I need to act?

-
0.36% chance of exploitation
EPSS score — low exploit probability
-
Not on CISA KEV list
No confirmed active exploitation reported to CISA
?
Patch status unknown
Check vendor advisories for fix availability and mitigation guidance
7
CVSS 7.5/10 High
NETWORK / LOW complexity

Affected Products (1)

Affected Vendors

Parseplatform

References (6)

Patch https://github.com/parse-community/parse-server/commit/4ac4b7f71002ed4fbedbb901d...
Release Notes https://github.com/parse-community/parse-server/releases/tag/4.10.4
Mitigation https://github.com/parse-community/parse-server/security/advisories/GHSA-7pr3-p5...
Patch https://github.com/parse-community/parse-server/commit/4ac4b7f71002ed4fbedbb901d...
Release Notes https://github.com/parse-community/parse-server/releases/tag/4.10.4
Mitigation https://github.com/parse-community/parse-server/security/advisories/GHSA-7pr3-p5...
32
/ 100
moderate-risk
Severity 26/34 · High
Exploitability 1/34 · Minimal
Exposure 5/34 · Minimal