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/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 |
https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36 | Issue Tracking Third Party Advisory |
Configurations
Information
Published : 2020-03-15 15:15
Updated : 2020-03-19 10:38
NVD link : CVE-2020-10594
Mitre link : CVE-2020-10594
JSON object : View
CWE
CWE-287
Improper Authentication
Products Affected
styria
- django-rest-framework-json_web_tokens