GHSA-pfj7-wv7c-22pr

Parse Server has an auth provider validation bypass on login via partial authData

En bref

Publiée
Mise à jour
CVE
CVE-2026-33409
Alias
BIT-parse-2026-33409
CVSS_V3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
CVSS_V4
CVSS:4.0/AV:N/AC:H/AT:P/PR:H/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Description

### Impact An authentication bypass vulnerability allows an attacker to log in as any user who has linked a third-party authentication provider, without knowing the user's credentials. The attacker only needs to know the user's provider ID to gain full access to their account, including a valid session token. This affects Parse Server deployments where the server option `allowExpiredAuthDataToken` is set to `true`. The default value is `false`. ### Patches Auth providers are now always validated on login, regardless of the `allowExpiredAuthDataToken` setting. The option `allowExpiredAuthDataToken` has been deprecated and will be removed in a future major version. ### Workarounds Set `allowExpiredAuthDataToken` to `false` (the default) or remove the option from the server configuration.

Paquets affectés

PaquetVersions
npm · parse-serverintroduced 9.0.0, fixed 9.6.0-alpha.41
npm · parse-serverintroduced 0, fixed 8.6.52

Références

Sources

SourceLicence
OSV.devCC-BY 4.0 — GitHub Advisory Database