Repository navigation
Replies: 1 comment
|
Please follow the security disclosure procedure if you believe this is a possible security vulnerability https://github.com/keycloak/keycloak/security. More on topic, I'm not sure whether the However, it may be possible to use the |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
During a recent assessment, I observed that KEYCLOAK is not generating new
AUTH_SESSION_IDandAUTH_SESSION_ID_LEGACYafter successful authentication. This behavior potentially exposes our application to a session fixation vulnerability.In a session fixation attack, an attacker creates a new session on a web application and records the associated session identifier. The attacker then causes the victim to authenticate against the server using the same session identifier, thereby gaining access to the user's account through the active session.
Given this context, could anyone provide insights or recommendations on the following:
I appreciate any insights or recommendations you can provide on this matter.
Best regards,
Sarthak Saxena
All reactions