Django REST framework: TokenProxy.delete() reports success and revokes nothing

[ Description ]Official description

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.

[ Fixes ]Fixes and patches

• djangorestframework 3.18.2Fixed version · GitHub Advisories · pip package djangorestframework: upgrade to 3.18.2 or later (affected >= 3.12.0, < 3.18.2)

[ Packages ]Affected open-source packages

• djangorestframework pipAffected >= 3.12.0, < 3.18.2 · fixed in 3.18.2 · GHSA-xw6w-gcfp-cf8m

[ References ]References

• github.com/encode/django-rest-framework/commit/af3fabfd517307fbc5d500fba1ab8f6e25f220b0
• github.com/encode/django-rest-framework/releases/tag/3.18.2
• github.com/encode/django-rest-framework/security/advisories/GHSA-xw6w-gcfp-cf8m