Skip to content

Protected fields exposed via LiveQuery

High severity GitHub Reviewed Published Jun 30, 2022 in parse-community/parse-server • Updated Jul 24, 2023

Package

npm parse-server (npm)

Affected versions

< 4.10.13
>= 5.0.0, < 5.2.4

Patched versions

4.10.13
5.2.4

Description

Impact

Parse Server LiveQuery does not remove protected fields in classes, passing them to the client.

Patches

The LiveQueryController now removes protected fields from the client response.

Workarounds

Use Parse.Cloud.afterLiveQueryEvent to manually remove protected fields.

References

For more information

If you have any questions or comments about this advisory:

References

@mtrezza mtrezza published to parse-community/parse-server Jun 30, 2022
Published by the National Vulnerability Database Jun 30, 2022
Published to the GitHub Advisory Database Jul 6, 2022
Reviewed Jul 6, 2022
Last updated Jul 24, 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
Low
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:L/A:N

EPSS score

0.150%
(52nd percentile)

CVE ID

CVE-2022-31112

GHSA ID

GHSA-crrq-vr9j-fxxh
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.