Enviar #857923: django-oauth django-oauth-toolkit 3.3.0 at commit ddec25b491e52d7f4a1e2cf13a436ffddcf6c782 CWE-613 Insufficient Session Expiration / CWE-287 Improper Autheinformación

Títulodjango-oauth django-oauth-toolkit 3.3.0 at commit ddec25b491e52d7f4a1e2cf13a436ffddcf6c782 CWE-613 Insufficient Session Expiration / CWE-287 Improper Authe
Descripcióndjango-oauth-toolkit 3.3.0 conditionally accepts expired ID tokens for OpenID Connect RP-initiated logout. When RP-initiated logout is enabled, the default OIDC_RP_INITIATED_LOGOUT_ACCEPT_EXPIRED_TOKENS=True makes _load_id_token() construct the JWT with an empty check_claims dictionary, explicitly skipping validation of exp and nbf. validate_logout_request_user() then uses the loaded IDToken for logout validation and client matching. This issue is conditional because RP-initiated logout must be enabled by the deployment. If enabled with the default expired-token option, stale id_token_hint values can participate in logout and token deletion flows after their intended validity period. Remediation should default expired-token acceptance to false or enforce a separate maximum acceptable ID token age for logout hints.
Fuente⚠️ https://github.com/django-oauth/django-oauth-toolkit/issues/1715
Usuario
 Galaxyn (UID 98388)
Sumisión2026-06-13 12:54 (hace 1 mes)
Moderación2026-07-18 10:23 (1 month later)
EstadoDuplicado
Entrada de VulDB380022 [django-oauth django-oauth-toolkit 3.3.0 oauth2_validators.py _load_id_token autenticación débil]
Puntos0

Are you interested in using VulDB?

Download the whitepaper to learn more about our service!