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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2020-0074 | 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. |
Github GHSA |
GHSA-fpjm-rp2g-3r4c | Django Rest Framework jwt allows obtaining new token from notionally invalidated token |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2024-08-04T11:06:09.995Z
Reserved: 2020-03-15T00:00:00
Link: CVE-2020-10594
No data.
Status : Modified
Published: 2020-03-15T22:15:14.130
Modified: 2024-11-21T04:55:39.787
Link: CVE-2020-10594
No data.
OpenCVE Enrichment
No data.
EUVD
Github GHSA