full-disclosure - Re: [Django] Cookie-based session storage session invalidation issue

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date: Wed, 2 Oct 2013 20:04:41 +0100
From: Paul McMillan <paul@...illan.ws>
To: full-disclosure@...ts.grok.org.uk
Subject: Re: [Django] Cookie-based session storage session
	invalidation issue

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@...cnamara.com>
> To: <full-disclosure@...ts.grok.org.uk>
> 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/