CVE-2020-10594

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
Configurations

Configuration 1 (hide)

cpe:2.3:a:styria:django-rest-framework-json_web_tokens:*:*:*:*:*:*:*:*

History

21 Nov 2024, 04:55

Type Values Removed Values Added
References () https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36 - Issue Tracking, Third Party Advisory () https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36 - Issue Tracking, Third Party Advisory
References () https://github.com/jpadilla/django-rest-framework-jwt/issues/484 - Issue Tracking, Third Party Advisory () https://github.com/jpadilla/django-rest-framework-jwt/issues/484 - Issue Tracking, Third Party Advisory
References () https://pypi.org/project/drf-jwt/1.15.1/#history - Release Notes, Third Party Advisory () https://pypi.org/project/drf-jwt/1.15.1/#history - Release Notes, Third Party Advisory

Information

Published : 2020-03-15 22:15

Updated : 2024-11-21 04:55


NVD link : CVE-2020-10594

Mitre link : CVE-2020-10594

CVE.ORG link : CVE-2020-10594


JSON object : View

Products Affected

styria

  • django-rest-framework-json_web_tokens
CWE
CWE-287

Improper Authentication