| 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
| ||
|
Message-ID: <CAAsS5mpMEWpbMrsRoxkQXCKWMdLOsc5OHWW97KVZZxUBpEP-Mw@mail.gmail.com>
Date: Tue, 24 Sep 2013 21:30:58 -0400
From: "G. S. McNamara" <main@...cnamara.com>
To: full-disclosure@...ts.grok.org.uk
Subject: [Ruby on Rails] Move away from CookieStore if you
care about your users and their security. Here is a technical explanation
why.
Ruby on Rails Web applications versions 2.0 through 4.0 are by default
vulnerable to an oft-overlooked Web application security issue: Session
cookies are valid for life.* A malicious user could use the stolen cookie
from any authenticated request by the user to log in as them at any point
in the future.
The fix is to configure your Rails app to store most session information on
the server side in the database. Move away from the default CookieStore,
which stores the entire session hash in the cookie, to something like
ActiveRecordStore.
Here is a full write-up if needed:
http://maverickblogging.com/logout-is-broken-by-default-ruby-on-rails-web-applications/
**In my testing, the only methods to invalidate these cookies are for the
user to change their password or for systems administrators to change the
application secret.*
G. S. McNamara
Content of type "text/html" skipped
_______________________________________________
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/
Powered by blists - more mailing lists