Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Session Fixation doc #1640

Merged
merged 4 commits into from
Oct 23, 2024
Merged

Update Session Fixation doc #1640

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
2177048
Update Session Fixation doc
alexisintech Oct 21, 2024
a2d8f68
Merge branch 'main' into aa/DOCS-9374
victoriaxyz Oct 22, 2024
9312eca
Merge branch 'main' into aa/DOCS-9374
victoriaxyz Oct 22, 2024
7a27000
Merge branch 'main' into aa/DOCS-9374
alexisintech Oct 23, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 3 additions & 9 deletions docs/security/fixation-protection.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,17 +1,11 @@
---
title: Fixation protection
description: Session Fixation is an attack that permits an attacker to hijack a valid user session. The attack explores a limitation in the way the web application manages the session ID, more specifically the vulnerable web application. When authenticating a user, it doesn’t assign a new session ID, making it possible to use an existent session ID.
description: Session fixation is an attack that permits an attacker to hijack a valid user session. The attack explores a limitation in the way the web application manages the session ID, more specifically the vulnerable web application. When authenticating a user, it doesn’t assign a new session ID, making it possible to use an existent session ID.
---

Session Fixation is an attack that permits an attacker to hijack a valid user session. The attack explores a limitation in the way the web application manages the session ID, more specifically the vulnerable web application. When authenticating a user, it doesn't assign a new session ID, making it possible to use an existent session ID.
Session fixation is a security vulnerability that allows an attacker to hijack a valid user session. This vulnerability arises when web applications reuse existing session IDs instead of generating new ones during the authentication process. By exploiting this flaw, attackers can potentially gain unauthorized access to a user's account and perform malicious actions on their behalf.

[The OWASP® Foundation, Cross Site Request Forgery (CSRF)](https://owasp.org/www-community/attacks/Session_fixation)

Session fixation is a technique for hijacking a user session.

Consider an attacker visits a public computer, navigates to `example.com` and starts the sign in process, but does not finish signing in. Before leaving the computer, the attacker inspects the session token and takes it with them.

Then, consider a victim sits at the same computer, navigates to `example.com`, and signs in with their own account.If `example.com` failed to reset the session token for the victim, then the attacker can hijack the victim's session and act on their behalf.
See the [OWASP Session Fixation](https://owasp.org/www-community/attacks/Session_fixation) page for specific examples of how this attack works.

## How does Clerk protect against session fixation?

Expand Down
Loading