CVE-2020-10594
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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (1.62%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.1
- 9.1 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- EPSS
- 1.62% probability · 75th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-287
- Affected
- styria/django-rest-framework-json web tokens
- Source
- cve@mitre.org
References
- https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36Issue Tracking, Third Party Advisory
- https://github.com/jpadilla/django-rest-framework-jwt/issues/484Issue Tracking, Third Party Advisory
- https://pypi.org/project/drf-jwt/1.15.1/#historyRelease Notes, Third Party Advisory
- https://github.com/Styria-Digital/django-rest-framework-jwt/issues/36Issue Tracking, Third Party Advisory
- https://github.com/jpadilla/django-rest-framework-jwt/issues/484Issue Tracking, Third Party Advisory
- https://pypi.org/project/drf-jwt/1.15.1/#historyRelease Notes, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.