spring-projects / spring-projects/spring-security
No session fixation protection on remember-me login
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.6k
- Forks
- 6.3k
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 52
Description
It appears that there is no session fixation strategy being called when the remember-me filter authenticates the user using the remember-me cookie. The session id remains the same. I'm not sure if this is exploitable. The only way i can think of is via url rewriting. How does servlet handle mixed cookie and url rewriting? For example, a remember me cookie with a rewritten URL.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the remember-me filter's authentication path and how it handles the session ID. Determine whether session fixation protection is invoked for remember-me cookie authentication, then define the expected behavior and add coverage if the project identifies a relevant test location.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100