Advisory

GHSA-2m6g-crv8-p3c6

Also known as: BIT-parse-2022-36079, CVE-2022-36079

Summary

Parse Server vulnerable to brute force guessing of user sensitive data via search patterns

Details

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:

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

Severity

High Basis: The source's own band: HIGH

Dates

Published
2022-09-16 21:17 UTC
Modified
2023-12-06 01:02 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 0, fixed 4.10.14 (semver)

Fixed versions

4.10.14

Fix

parse-server

npm · All systems

Affected

  • introduced 5.0.0, fixed 5.2.5 (semver)

Fixed versions

5.2.5

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences