Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to 9.6.0-alpha.11 and 8.6.37, Parse Servers built-in OAuth2 auth adapter exports a singleton instance that is reused directly across all OAuth2 provider configurations. Under concurrent authentication requests for different OAuth2 providers, one providers token validation may execute using another providers configuration, potentially allowing a token that should be rejected by one provider to be accepted because it is validated against a different providers policy. Deployments that configure multiple OAuth2 providers via the oauth2: true flag are affected. This vulnerability is fixed in 9.6.0-alpha.11 and 8.6.37.
Weakness
The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Parse-server | Parseplatform | * | 8.6.37 (excluding) |
| Parse-server | Parseplatform | 9.0.0 (including) | 9.6.0 (excluding) |
| Parse-server | Parseplatform | 9.6.0-alpha1 (including) | 9.6.0-alpha1 (including) |
| Parse-server | Parseplatform | 9.6.0-alpha10 (including) | 9.6.0-alpha10 (including) |
| Parse-server | Parseplatform | 9.6.0-alpha2 (including) | 9.6.0-alpha2 (including) |
| Parse-server | Parseplatform | 9.6.0-alpha3 (including) | 9.6.0-alpha3 (including) |
| Parse-server | Parseplatform | 9.6.0-alpha4 (including) | 9.6.0-alpha4 (including) |
| Parse-server | Parseplatform | 9.6.0-alpha5 (including) | 9.6.0-alpha5 (including) |
| Parse-server | Parseplatform | 9.6.0-alpha6 (including) | 9.6.0-alpha6 (including) |
| Parse-server | Parseplatform | 9.6.0-alpha7 (including) | 9.6.0-alpha7 (including) |
| Parse-server | Parseplatform | 9.6.0-alpha8 (including) | 9.6.0-alpha8 (including) |
| Parse-server | Parseplatform | 9.6.0-alpha9 (including) | 9.6.0-alpha9 (including) |
Extended Description
A race condition occurs within concurrent environments, and it is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc. A race condition violates these properties, which are closely related:
A race condition exists when an “interfering code sequence” can still access the shared resource, violating exclusivity. The interfering code sequence could be “trusted” or “untrusted.” A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.
Potential Mitigations
- Minimize the usage of shared resources in order to remove as much complexity as possible from the control flow and to reduce the likelihood of unexpected conditions occurring.
- Additionally, this will minimize the amount of synchronization necessary and may even help to reduce the likelihood of a denial of service where an attacker may be able to repeatedly trigger a critical section (CWE-400).