Vulnerability Details : CVE-2020-10594
An issue was discovered in drf-jwt 1.15.x before 1.15.1. It allows attackers with access to a notionally invalidated token to obtain a new, working token via the refresh endpoint, because the blacklist protection mechanism is incompatible with the token-refresh feature. NOTE: drf-jwt is a fork of jpadilla/django-rest-framework-jwt, which is unmaintained.
Vulnerability category: BypassGain privilege
Products affected by CVE-2020-10594
- Styria » Django-rest-framework-json Web TokensVersions from including (>=) 1.15.0 and before (<) 1.15.1cpe:2.3:a:styria:django-rest-framework-json_web_tokens:*:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2020-10594
0.28%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 49 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2020-10594
| Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
|---|---|---|---|---|---|---|
|
5.8
|
MEDIUM | AV:N/AC:M/Au:N/C:P/I:P/A:N |
8.6
|
4.9
|
NIST | |
|
9.1
|
CRITICAL | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
3.9
|
5.2
|
NIST |
CWE ids for CVE-2020-10594
-
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.Assigned by: nvd@nist.gov (Primary)
References for CVE-2020-10594
-
https://pypi.org/project/drf-jwt/1.15.1/#history
drf-jwt · PyPIRelease Notes;Third Party Advisory
-
https://github.com/jpadilla/django-rest-framework-jwt/issues/484
Status · Issue #484 · jpadilla/django-rest-framework-jwt · GitHubIssue Tracking;Third Party Advisory
-
https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36
Blacklisted tokens can still be refreshed · Issue #36 · Styria-Digital/django-rest-framework-jwt · GitHubIssue Tracking;Third Party Advisory
Jump to