نسخههای متأثر
npmnocodb
- نسخههای متأثر
- <= 0.301.2
- نسخهٔ اصلاحشده
- 0.301.3
بهرهبرداری
شرح آسیبپذیری
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).
پیوندها
- https://github.com/advisories/GHSA-x4vh-j75g-268g
- https://github.com/nocodb/nocodb
- https://github.com/nocodb/nocodb/commit/dfbe836577354ba780563a5cf8cb50bfc61a203e
- https://github.com/nocodb/nocodb/releases/tag/0.301.3
- https://github.com/nocodb/nocodb/security/advisories/GHSA-x4vh-j75g-268g
- https://nvd.nist.gov/vuln/detail/CVE-2026-28396
گزارشدهندگان
- bugbunny-research
- zuhairhalawa

