CVE-2020-10594Published Mar 15, 2020 · Mar 15Updated Nov 10
| Product | Affected | Fixed in |
|---|---|---|
| drf-jwt PyPI |
|
|
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.
From the CVE record · mitre
In drf-jwt 1.15.0, the blacklist protection mechanism is incompatible with token refresh. An attacker with access to a notionally invalidated token can use the refresh endpoint to obtain a new, working token.
Check applications using the PyPI drf-jwt package version 1.15.0.