Protected fields exposed via LiveQuery in parse-server
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.
01
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… | ||||
02
references
External citations — patches, advisories, analysis.
- https://github.com/parse-community/parse-server/commit/309f64ced8700321df056fb3cc97f15007a00df1ADVISORY
- https://github.com/parse-community/parse-server/commit/9fd4516cde5c742f9f29dd05468b4a43a85639a6ADVISORY
- https://github.com/parse-community/parse-server/issues/8073ADVISORY
- https://github.com/parse-community/parse-server/pull/8074ADVISORY
- https://github.com/parse-community/parse-server/releases/tag/5.2.4ADVISORY
- https://github.com/parse-community/parse-server/security/advisories/GHSA-crrq-vr9j-fxxhADVISORY
- https://nvd.nist.gov/vuln/detail/CVE-2022-31112WEB
scry
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