Encode django-rest-framework
Django REST framework: TokenProxy.delete() reports success and revokes nothing
Django REST framework is a toolkit for building Web APIs. From 3.12.0 until 3.18.2, TokenProxy.delete() in rest_framework/authtoken/models.py uses the proxy's user-id pk while the concrete Token token-string primary key identifies rows, so Django issues a deletion query that matches no row and reports zero deletions without raising an error. Applications, administrative integrations, or operational scripts that revoke credentials through a TokenProxy instance can therefore believe revocation succeeded while the token remains live and continues authenticating. DRF's own TokenAdmin.delete_model workaround is not affected, but other callers can leave access available indefinitely because DRF tokens do not expire automatically. This issue is fixed in version 3.18.2.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.12.0, < 3.18.2
Fixed in 3.18.2
Mitigation
Upgrade django-rest-framework to 3.18.2 or later.
References
- Vendor advisory github.com/encode/django-rest-framework/securi…
- Patch github.com/encode/django-rest-framework/commit…
- Release notes github.com/encode/django-rest-framework/releas…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.