NocoDB's Refresh Tokens Not Revoked on Password Reset

Summary

The password reset flow did not revoke existing refresh tokens, allowing an attacker with a previously stolen refresh token to continue minting valid JWTs after the victim resets their password.

Details

passwordReset() in users.service.ts updated token_version (invalidating JWTs) but did not call UserRefreshToken.deleteAllUserToken(). The refreshToken() method only checked token existence, not token_version. Both passwordChange() and signOut() correctly deleted all refresh tokens.

Impact

An attacker who previously obtained a refresh token retains access after password reset until the token expires.

Credit

This issue was reported by @bugbunny-research (bugbunny.ai).