First published: Fri Sep 23 2022(Updated: )
Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. In versions prior to 4.10.16, or from 5.0.0 to 5.2.6, validation of the authentication adapter app ID for _Facebook_ and _Spotify_ may be circumvented. Configurations which allow users to authenticate using the Parse Server authentication adapter where `appIds` is set as a string instead of an array of strings authenticate requests from an app with a different app ID than the one specified in the `appIds` configuration. For this vulnerability to be exploited, an attacker needs to be assigned an app ID by the authentication provider which is a sub-set of the server-side configured app ID. This issue is patched in versions 4.10.16 and 5.2.7. There are no known workarounds.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Parseplatform Parse-server | <4.10.16 | |
Parseplatform Parse-server | >=5.0.0<5.2.7 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The vulnerability ID for this Parse Server vulnerability is CVE-2022-39231.
The severity of CVE-2022-39231 is low.
Versions prior to 4.10.16, or from 5.0.0 to 5.2.6 of Parse Server are affected by CVE-2022-39231.
An attacker can exploit the vulnerability described in CVE-2022-39231 by circumventing the authentication adapter app ID validation for Facebook and Spotify.
Yes, a fix is available for CVE-2022-39231. It is recommended to update to version 4.10.16 or higher, or version 5.2.7 or higher of Parse Server to mitigate this vulnerability.