Fix session persistence sql vulnerabilities #341
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PROBLEM
id
andpersistence_token
in the rails session cookie.find_by_*
methods when looking upid
andpersistence_token
.find_by_*
methods accept option hashes, such as:select => "..."
.This leaves
persist_by_session
open to sql attacks (such as logging in as any user), if a malicious user can write their own rails session cookie (if they have the rails secret_token).Although authlogic verifies a user's identity with
persistence_token
stored in the database, this can currently be surpassed using this vulnerability, renderingpersistence_token
useless.SOLUTION
Use
to_s
on the session credentials when looking up a user.