Filtered by vendor Parseplatform
Subscribe
Total
27 CVE
| CVE | Vendors | Products | Updated | CVSS v2 | CVSS v3 |
|---|---|---|---|---|---|
| CVE-2021-41109 | 1 Parseplatform | 1 Parse-server | 2021-10-08 | 4.3 MEDIUM | 7.5 HIGH |
| Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to version 4.10.4, for regular (non-LiveQuery) queries, the session token is removed from the response, but for LiveQuery payloads it is currently not. If a user has a LiveQuery subscription on the `Parse.User` class, all session tokens created during user sign-ups will be broadcast as part of the LiveQuery payload. A patch in version 4.10.4 removes session tokens from the LiveQuery payload. As a workaround, set `user.acl(new Parse.ACL())` in a beforeSave trigger to make the user private already on sign-up. | |||||
| CVE-2020-26288 | 1 Parseplatform | 1 Parse-server | 2021-01-04 | 4.0 MEDIUM | 6.5 MEDIUM |
| Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. It is an npm package "parse-server". In Parse Server before version 4.5.0, user passwords involved in LDAP authentication are stored in cleartext. This is fixed in version 4.5.0 by stripping password after authentication to prevent cleartext password storage. | |||||
| CVE-2020-15270 | 1 Parseplatform | 1 Parse-server | 2020-10-30 | 4.0 MEDIUM | 4.3 MEDIUM |
| Parse Server (npm package parse-server) broadcasts events to all clients without checking if the session token is valid. This allows clients with expired sessions to still receive subscription objects. It is not possible to create subscription objects with invalid session tokens. The issue is not patched. | |||||
| CVE-2019-1020013 | 1 Parseplatform | 1 Parse-server | 2020-08-24 | 5.0 MEDIUM | 5.3 MEDIUM |
| parse-server before 3.6.0 allows account enumeration. | |||||
| CVE-2020-15126 | 1 Parseplatform | 1 Parse Server | 2020-07-28 | 4.0 MEDIUM | 6.5 MEDIUM |
| In parser-server from version 3.5.0 and before 4.3.0, an authenticated user using the viewer GraphQL query can by pass all read security on his User object and can also by pass all objects linked via relation or Pointer on his User object. | |||||
| CVE-2020-5251 | 1 Parseplatform | 1 Parse-server | 2020-03-06 | 5.0 MEDIUM | 5.3 MEDIUM |
| In parser-server before version 4.1.0, you can fetch all the users objects, by using regex in the NoSQL query. Using the NoSQL, you can use a regex on sessionToken and find valid accounts this way. | |||||
| CVE-2019-1020012 | 1 Parseplatform | 1 Parse-server | 2019-08-02 | 5.0 MEDIUM | 7.5 HIGH |
| parse-server before 3.4.1 allows DoS after any POST to a volatile class. | |||||