Protected fields exposed via LiveQuery
### 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 - https://github.com/parse-community/parse-server/security/advisories/GHSA-crrq-vr9j-fxxh - https://github.com/parse-community/parse-server ### For more information If you have any questions or comments about this advisory: - For questions or comments about this vulnerability visit our [community forum](http://community.parseplatform.org/) or [community chat](http://chat.parseplatform.org/) - Report other vulnerabilities at [report.parseplatform.org](https://report.parseplatform.org/)
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2022-31112US | high8.2 | — | ||
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… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/parse-community/parse-serverPACKAGE
- https://github.com/parse-community/parse-server/commit/054f3e6ab01d66a0dcfb77725af28eac1485b375WEB
- https://github.com/parse-community/parse-server/commit/309f64ced8700321df056fb3cc97f15007a00df1WEB
- https://github.com/parse-community/parse-server/commit/9fd4516cde5c742f9f29dd05468b4a43a85639a6WEB
- https://github.com/parse-community/parse-server/issues/8073WEB
- https://github.com/parse-community/parse-server/pull/8074WEB
- https://github.com/parse-community/parse-server/releases/tag/5.2.4WEB
- https://github.com/parse-community/parse-server/security/advisories/GHSA-crrq-vr9j-fxxhWEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan