| 标题 | nocodb <= 2026.07.0 Improper Restriction of Excessive Authentication Attempts |
|---|
| 描述 | NocoDB's self-hosted (CE/OSS) build ships PublicApiLimiterGuard as a pass-through stub that returns true for every request, and binds no ThrottlerGuard at the application level. This guard is the only guard protecting /auth/user/signup, /auth/user/signin, /auth/password/forgot and /auth/token/validate/:tokenId.
Three defects compose into a full account takeover:
Enumeration oracle — the signup endpoint returns HTTP 400 User already exist for a registered address and HTTP 200 (with a JWT) for an unregistered one, giving an attacker a precise, unauthenticated test for account existence.
No authentication rate limiting — the sign-in endpoint accepts unlimited failed attempts with no throttling, no account lockout, and no backoff.
Length-only password policy — validatePassword() enforces only length >= 8, with no complexity requirement and no weak-password blocklist, so passwords such as 12345678 and password are accepted at registration.
An attacker enumerates valid accounts, then brute-forces each at full network speed against passwords that the product itself permits. The resulting JWT grants full API access as the victim. |
|---|
| 来源 | ⚠️ https://github.com/nocodb/nocodb/issues/14688 |
|---|
| 用户 | ZAST.AI (UID 87884) |
|---|
| 提交 | 2026-09-29 10時56分 (1 月前) |
|---|
| 管理 | 2026-10-25 10時23分 (26 days later) |
|---|
| 状态 | 已接受 |
|---|
| VulDB条目 | 426191 [NocoDB 直到 2026.07.0 /auth/user/signup validatePassword 信息公开] |
|---|
| 积分 | 20 |
|---|