#25847: is_authenticated is vulnerability-prone.
-------------------------------+--------------------
Reporter: skorokithakis | Owner: nobody
Type: Uncategorized | Status: new
Component: contrib.auth | Version: 1.9
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------
There's an inconsistency between `is_authenticated` and `is_superuser`.
The former is a method and the latter is a property, leading many people
to do:
{{{
if request.user.is_authenticated:
return sensitive_information
}}}
which is, of course, always executed.
I propose that is_authenticated be turned into a property, while it can
also be a callable, for backwards-compatibility.
--
Ticket URL: <https://code.djangoproject.com/ticket/25847>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/056.349c165e8ddf1e8d390cede946c9484d%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
