Budibase: Account Enumeration via Login Lockout Response Differential
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Budibase | budibase | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Budibase | Budibase |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-cr7p-cr3q-h5cm | Budibase: Account Enumeration via Login Lockout Response Differential |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.438% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Budibase
Budibase budibase |
|
| Vendors & Products |
Budibase
Budibase budibase |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Budibase is an open-source low-code platform. Prior to 3.39.25, POST /api/global/auth/:tenantId/login incremented the failure counter in packages/worker/src/api/controllers/global/auth.ts only for existing users, while packages/worker/src/middleware/emailLockout.ts returned X-Account-Locked and Retry-After only for locked identifiers. An unauthenticated attacker could compare the response after repeated failures to enumerate valid email addresses and temporarily lock valid accounts. This issue is fixed in version 3.39.25. | |
| Title | Budibase: Account Enumeration via Login Lockout Response Differential | |
| Weaknesses | CWE-204 | |
| References |
| |
| Metrics |
cvssV3_1
|