Description
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 (3)
Core 3
Core References
Issue Tracking, Third Party Advisory x_refsource_misc
https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36
Release Notes, Third Party Advisory x_refsource_misc
https://pypi.org/project/drf-jwt/1.15.1/#history
Issue Tracking, Third Party Advisory x_refsource_misc
https://github.com/jpadilla/django-rest-framework-jwt/issues/484
Scores
CVSS v3
9.1
EPSS
0.0126
EPSS Percentile
65.8%
Attack Vector
NETWORK
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Details
CWE
CWE-287
Status
published
Products (2)
pypi/drf-jwt
1.15.0 - 1.15.1PyPI
styria/django-rest-framework-json_web_tokens
1.15.0 - 1.15.1
Published
Mar 15, 2020
Tracked Since
Feb 18, 2026