CVE-2022-36079

Description

### Impact Internal fields (keys used internally by Parse Server, prefixed by `_`) and protected fields (user defined) can be used as query constraints. Internal and protected fields are removed by Parse Server from query results and are only returned to the client using a valid master key. However, using query constraints, these fields can be guessed by enumerating until Parse Server returns a response object. ### Patches The patch requires the master key to use internal and protected fields as query constraints. ### Workarounds Implement a Parse Cloud Trigger `beforeFind` and manually remove the query constraints, such as: ```js Parse.Cloud.beforeFind('TestObject', ({ query }) => { for (const key in query._where || []) { // Repeat logic for protected fields if (key.charAt(0) === '_') { delete query._where[key]; } } }); ``` ### References - https://github.com/parse-community/parse-server/security/advisories/GHSA-2m6g-crv8-p3c6

How to fix CVE-2022-36079

To remediate CVE-2022-36079, upgrade the affected package to a fixed version below.

• —upgrade to 4.10.14 or later
• —upgrade to 4.10.14 or later

Is CVE-2022-36079 being exploited?

Low — EPSS is 0.6%, meaning exploitation activity has not been observed at scale.

Affected packages (2)

• from 0, < 4.10.14, >= 5.0.0, < 5.2.5
• from 0, < 4.10.14

CVSS scores

References (9)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2022-36079
• PATCHgithub.com/parse-community/parse-server
• WEBgithub.com/parse-community/parse-server/commit/634c44acd18f6ee6ec60fac89a2b602d92799bec
• WEBgithub.com/parse-community/parse-server/commit/e39d51bd329cd978589983bd659db46e1d45aad4