[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Full-disclosure] [Django] Cookie-based session storage session invalidation issue
- To: full-disclosure@xxxxxxxxxxxxxxxxx
- Subject: Re: [Full-disclosure] [Django] Cookie-based session storage session invalidation issue
- From: Paul McMillan <paul@xxxxxxxxxxx>
- Date: Wed, 2 Oct 2013 20:04:41 +0100
G. S. McNamara:
Perhaps next you will disclose that if an attacker obtains a user's
password, they can log in as that user. Seriously, "full disclosure"
of well documented behavior is not particularly impressive.
https://docs.djangoproject.com/en/1.5/topics/http/sessions/#using-cookie-based-sessions
Cheers,
-Paul
> From: "G. S. McNamara" <main@xxxxxxxxxxxxxx>
> To: <full-disclosure@xxxxxxxxxxxxxxxxx>
> Subject: [Full-disclosure] [Django] Cookie-based session storage session
> invalidation issue
>
> FD,
>
> I’m back!
>
> Django versions 1.4 – 1.7 offer a cookie-based session storage option (not
> the default > this time) that is afflicted by the same issue I posted about
> previously concerning Ruby > on Rails:
>
> If you obtain a user’s cookie, even if they log out, you can still log in as
> them.
>
> The short write-up is here, if needed:
> http://maverickblogging.com/security-vulnerability-with-django-cookie-based-sessions/
>
> Cheers,
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/