Security:Session fixation: Difference between revisions
Helen Foster (talk | contribs) (stub template) |
No edit summary |
||
| Line 5: | Line 5: | ||
==What is the danger?== | ==What is the danger?== | ||
"Session Fixation is an attack that permits an attacker to hijack a valid user session. (...) . The attack consists of obtaining a valid session ID (e.g. by connecting to the application), inducing a user to authenticate himself with that session ID, and then hijacking the user-validated session by the knowledge of the used session ID. The attacker has to provide a legitimate Web application session ID and try to make the victim's browser use it. (...) The session fixation attack is a class of Session Hijacking, which steals the established session between the client and the Web Server after the user logs in. Instead, the Session Fixation attack fixes an established session on the victim's browser, so the attack starts before the user logs in. " (OWASP - Session fixation) | |||
==How Moodle avoids this problem== | ==How Moodle avoids this problem== | ||
Revision as of 12:54, 20 August 2018
This page forms part of the Moodle security guidelines.
What is the danger?
"Session Fixation is an attack that permits an attacker to hijack a valid user session. (...) . The attack consists of obtaining a valid session ID (e.g. by connecting to the application), inducing a user to authenticate himself with that session ID, and then hijacking the user-validated session by the knowledge of the used session ID. The attacker has to provide a legitimate Web application session ID and try to make the victim's browser use it. (...) The session fixation attack is a class of Session Hijacking, which steals the established session between the client and the Web Server after the user logs in. Instead, the Session Fixation attack fixes an established session on the victim's browser, so the attack starts before the user logs in. " (OWASP - Session fixation)
