Accepting session_id generated on the outside, when using MemCacheStore as SessionStorage
Reported by tmtysk | July 8th, 2008 @ 06:06 AM | in 2.x
In CGI::Session::MemCache,
When using MemCacheStore as SessionStorage, if we created invalid session_id on the outside and requested to rails-application including it, then, server accepts it and response Set-Cookie header including that session_id.
For example:
$ curl -I http://localhost:3000/?_sess=foobar
HTTP/1.1 200 Ok
Connection: close
Date: Tue, 08 Jul 2008 04:59:36 GMT
Set-Cookie: _sess=foobar; path=/
:(omit the rest)
This behavior might be misused by session fixation attacks.
Comments and changes to this ticket
-
tmtysk October 23rd, 2008 @ 04:23 PM
- → Title changed from “Accepting session_id generated on the outside using MemCacheStore” to “Accepting session_id generated on the outside, when using MemCacheStore as SessionStorage”
-
tmtysk July 8th, 2008 @ 06:10 AM
In CGI::Session::MemCache,
When using MemCacheStore as SessionStorage, if we created invalid session_id on the outside and requested to rails-application including it, then, server accepts it and response Set-Cookie header including that session_id.
For example:
$ curl -I http://localhost:3000/?_sess=foobar
HTTP/1.1 200 Ok
Connection: close
Date: Tue, 08 Jul 2008 04:59:36 GMT
Set-Cookie: _sess=foobar; path=/
:(omit the rest)
This behavior might be misused by session fixation attacks.
Please Login or create a free account to add a new comment.
You can update this ticket by sending an email to from your email client. (help)
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
Source available from github
The Git repository resides at http://github.com/rails
Check out the current development trunk (Edge Rails) with:
git clone git://github.com/rails/rails.git
Creating or reviewing a patch
See the contributor guide.
Creating a feature request
Please don't. If you want a new feature in Rails, you'll have to pull up your sleeves and get busy yourself. Or convince someone else to do it. See the contributor guide on how to get going. But posting them here is just going to lead to ticket root.
Creating a bug report
When creating a bug report, be sure to include as much relevant information as possible. Post the code sample that causes the problem. Preferably, alter the unit tests and show through either changed or added tests how the expected behavior is not occuring.
Security vulnerabilities should be reported via an email to security@rubyonrails.org, do not use trac for reporting security vulnerabilities. All content in trac is publicly available as soon as it is posted.
Then don't get your hopes up. Unless you have a "Code Red, Mission Critical, The World is Coming to an End" kinda bug, you're creating this ticket in the hope that others with the same problem will be able to collaborate with you on solving it. Do not expect that the ticket automatically will see any activity or that others will jump to fix it. Creating a ticket like this is mostly to help yourself start on the path of fixing the problem and for others to sign on to with a "I'm having this problem too".
