Safety vulnerability ID: 38073
The information on this page was manually curated by our Cybersecurity Intelligence Team.
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. See: CVE-2020-10594.
Latest version: 1.19.2
JSON Web Token based authentication for Django REST framework
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.
MISC:https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36: https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36
MISC:https://github.com/jpadilla/django-rest-framework-jwt/issues/484: https://github.com/jpadilla/django-rest-framework-jwt/issues/484
MISC:https://pypi.org/project/drf-jwt/1.15.1/#history: https://pypi.org/project/drf-jwt/1.15.1/#history
Scan your Python project for dependency vulnerabilities in two minutes
Scan your application