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.
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
Link | Tags |
---|---|
https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36 | issue tracking third party advisory |
https://pypi.org/project/drf-jwt/1.15.1/#history | third party advisory release notes |
https://github.com/jpadilla/django-rest-framework-jwt/issues/484 | issue tracking third party advisory |