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
- https://nvd.nist.gov/vuln/detail/CVE-2020-10594
- https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36
- https://github.com/jpadilla/django-rest-framework-jwt/issues/484
- https://github.com/Styria-Digital/django-rest-framework-jwt/commit/868b5c22ddad59772b447080183e7c7101bb18e0
- https://pypi.org/project/drf-jwt/1.15.1/#history
- https://github.com/advisories/GHSA-fpjm-rp2g-3r4c