Skip to content

LiveQuery publishes user session tokens in parse-server

High severity GitHub Reviewed Published Sep 30, 2021 in parse-community/parse-server • Updated Feb 1, 2023

Package

npm parse-server (npm)

Affected versions

< 4.10.4

Patched versions

4.10.4

Description

Impact

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.

Patches

Remove session token from LiveQuery payload.

Workaround

Set user.acl(new Parse.ACL()) in a beforeSave trigger to make the user private already on sign-up.

References

@mtrezza mtrezza published to parse-community/parse-server Sep 30, 2021
Published by the National Vulnerability Database Sep 30, 2021
Reviewed Sep 30, 2021
Published to the GitHub Advisory Database Sep 30, 2021
Last updated Feb 1, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

EPSS score

0.137%
(50th percentile)

Weaknesses

CVE ID

CVE-2021-41109

GHSA ID

GHSA-7pr3-p5fm-8r9x

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.