Parse Server: Malicious Tokens Can Bypass Authentication

Summary

Parse Server's authentication system had a flaw that allowed attackers to use valid tokens from other apps to access accounts. This has been fixed in versions 8.6.10 and 9.5.0-alpha.11. Update to a patched version to prevent unauthorized access.

What to do

Update parse-server to version 9.5.0-alpha.11.
Update parse-server to version 8.6.10.

Affected software

Vendor	Product	Affected versions	Fix available
–	parse-server	> 9.0.0-alpha.1 , <= 9.5.0-alpha.11	9.5.0-alpha.11
–	parse-server	<= 8.6.10	8.6.10
parseplatform	parse-server	<= 8.6.10	–
parseplatform	parse-server	> 9.0.0 , <= 9.5.0	–
parseplatform	parse-server	9.5.0	–
parseplatform	parse-server	9.5.0	–
parseplatform	parse-server	9.5.0	–
parseplatform	parse-server	9.5.0	–
parseplatform	parse-server	9.5.0	–
parseplatform	parse-server	9.5.0	–
parseplatform	parse-server	9.5.0	–
parseplatform	parse-server	9.5.0	–
parseplatform	parse-server	9.5.0	–
parseplatform	parse-server	9.5.0	–

Original title

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.10 and 9.5.0-alpha.11, the Google, Apple, and Facebook authentication a...

Original description

Parse Server is an open source backend that can be deployed to any infrastructure that can run Node.js. Prior to versions 8.6.10 and 9.5.0-alpha.11, the Google, Apple, and Facebook authentication adapters use JWT verification to validate identity tokens. When the adapter's audience configuration option is not set (clientId for Google/Apple, appIds for Facebook), JWT verification silently skips audience claim validation. This allows an attacker to use a validly signed JWT issued for a different application to authenticate as any user on the target Parse Server. This issue has been patched in versions 8.6.10 and 9.5.0-alpha.11.

nvd CVSS4.0 9.3

Vulnerability type

CWE-287 Improper Authentication

CWE-863 Incorrect Authorization