Protected fields exposed via LiveQuery in parse-server
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 8.2epss 1.3%
exploitation probability
1.3%top 31% of all CVEs
observed exploitation
nono source reports it
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In affected versions parse Server LiveQuery does not remove protected fields in classes, passing them to the client. The LiveQueryController now removes protected fields from the client response. Users are advised to upgrade. Users unable t upgrade should use `Parse.Cloud.afterLiveQueryEvent` to manually remove protected fields.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N
Affected products
parse-community · parse-serverReferences
https://github.com/parse-community/parse-server/commit/309f64ced8700321df056fb3cc97f15007a00df1https://github.com/parse-community/parse-server/commit/9fd4516cde5c742f9f29dd05468b4a43a85639a6https://github.com/parse-community/parse-server/issues/8073https://github.com/parse-community/parse-server/pull/8074https://github.com/parse-community/parse-server/releases/tag/5.2.4https://github.com/parse-community/parse-server/security/advisories/GHSA-crrq-vr9j-fxxh