GHSA-jpq4-7fmq-q5fj parse-server: MFA SMS one-time password accepted twice under concurrent login

• npm parse-server: >= 9.0.0, < 9.9.0-alpha.2 → fixed in 9.9.0-alpha.2 • npm parse-server: < 8.6.76 → fixed in 8.6.76

Impact A race condition in the MFA SMS one-time password (OTP) login path allows two concurrent `/login` requests carrying the same OTP to both succeed and both receive valid session tokens, breaking the single-use property of the OTP. The vulnerability requires the attacker to already possess the victim's password and intercept the active SMS OTP (e.g. via SIM swap, network mirror, or phishing relay) and to race the legitimate login request, so the practical attack surface is narrow. This advisory is the same class of incomplete fix as GHSA-2299-ghjr-6vjp (TOTP recovery codes) and GHSA-w73w-g5xw-rwhf (MFA recovery in authData-only login). Those previous fixes added optimistic locking only for array-typed authData fields; SMS MFA stores the OTP as a string, so the guard skipped it. Patches The optimistic lock has been generalized to cover primitive (string, number, boolean) and array authData fields. The lock is implemented as a shared helper `applyAuthDataOptimisticLock` that adds equality predicates on the original values of changed fields to the update WHERE clause. Concurrent writers racing the same single-use token now miss the WHERE condition and surface as `Invalid auth data`. Workarounds • Disable SMS MFA and use TOTP instead (TOTP tokens are time-window validated, not stored single-use). • Place a rate limiter on the `/login` endpoint to reduce concurrent-request burst capacity. Resources • GitHub security advisory: https://github.com/parse-community/parse-server/security/advisories/GHSA-jpq4-7fmq-q5fj • Fix Parse Server 9: https://github.com/parse-community/parse-server/pull/10448 • Fix Parse Server 8: https://github.com/parse-community/parse-server/pull/10449