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.
References
Link | Resource |
---|---|
https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36 | Issue Tracking Third Party Advisory |
https://github.com/jpadilla/django-rest-framework-jwt/issues/484 | Issue Tracking Third Party Advisory |
https://pypi.org/project/drf-jwt/1.15.1/#history | Release Notes Third Party Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2020-03-15T21:22:09
Updated: 2020-03-15T21:22:09
Reserved: 2020-03-15T00:00:00
Link: CVE-2020-10594
JSON object: View
NVD Information
Status : Analyzed
Published: 2020-03-15T22:15:14.130
Modified: 2020-03-19T17:38:14.110
Link: CVE-2020-10594
JSON object: View
Redhat Information
No data.
CWE