Login Attempt Limit Bypass via Diacritic Handling
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| allauth | django-allauth | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Allauth | Django-allauth |
|
Vendor Solution
Upgrade django-allauth to version 65.19.4 (latest).
Vendor Workaround
The vulnerability is NOT exposed if any of the following settings is enabled. 65.4 and later: ACCOUNT_LOGIN_METHODS = {"email"} 65.3 and earlier: ACCOUNT_AUTHENTICATION_METHOD = "email"
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.226% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Login Attempt Limit Bypass via Diacritic Handling |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Allauth
Allauth django-allauth |
|
| Vendors & Products |
Allauth
Allauth django-allauth |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | django-allauth before 65.19.4 does not have the expected limits on failed login attempts because, in some common configurations, an attacker can leverage the handling of diacritics (e.g., accents) for a higher effective limit. | |
| Weaknesses | CWE-180 | |
| References |
|
|
| Metrics |
cvssV3_1
|