critical9.1
CVE-2020-10594
Django Rest Framework jwt allows obtaining new token from notionally invalidated token
Impact
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.
Affected packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| pip | drf-jwt | >= 1.15.0, < 1.15.1 | 1.15.1 |
Affected products
| Vendor | Product | Affected versions |
|---|---|---|
| Styria | Django-Rest-Framework-Json Web Tokens | from 1.15.0 before 1.15.1 |
Weakness classification
References
- NVD record
- CVE.org record
- GitHub advisory
- https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36
- https://github.com/jpadilla/django-rest-framework-jwt/issues/484
- https://pypi.org/project/drf-jwt/1.15.1/#history
- https://github.com/advisories/GHSA-fpjm-rp2g-3r4c
- https://nvd.nist.gov/vuln/detail/CVE-2020-10594
- https://github.com/Styria-Digital/django-rest-framework-jwt/commit/868b5c22ddad59772b447080183e7c7101bb18e0
- https://github.com/pypa/advisory-database/tree/main/vulns/drf-jwt/PYSEC-2020-40.yaml