Skip to content

Django Rest Framework jwt allows obtaining new token from notionally invalidated token

Critical severity GitHub Reviewed Published Jun 5, 2020 to the GitHub Advisory Database • Updated Aug 23, 2023

Package

pip drf-jwt (pip)

Affected versions

< 1.15.1

Patched versions

1.15.1

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

Published by the National Vulnerability Database Mar 15, 2020
Reviewed Jun 4, 2020
Published to the GitHub Advisory Database Jun 5, 2020
Last updated Aug 23, 2023

Severity

Critical
9.1
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Weaknesses

CVE ID

CVE-2020-10594

GHSA ID

GHSA-fpjm-rp2g-3r4c
Checking history
See something to contribute? Suggest improvements for this vulnerability.