A session fixation issue was discovered in the SAML adapters provided by Keycloak. The session ID and JSESSIONID cookie are not changed at login time, even when the turnOffChangeSessionIdOnLogin option is configured. This flaw allows an attacker who hijacks the current session before authentication to trigger session fixation.
Workaround:
Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHSA-2024:6493 | vendor advisory mailing list |
https://access.redhat.com/errata/RHSA-2024:6494 | vendor advisory mailing list |
https://access.redhat.com/errata/RHSA-2024:6495 | vendor advisory mailing list |
https://access.redhat.com/errata/RHSA-2024:6497 | vendor advisory mailing list |
https://access.redhat.com/errata/RHSA-2024:6499 | vendor advisory mailing list |
https://access.redhat.com/errata/RHSA-2024:6500 | vendor advisory mailing list |
https://access.redhat.com/errata/RHSA-2024:6501 | vendor advisory mailing list |
https://access.redhat.com/errata/RHSA-2024:6502 | vendor advisory mailing list |
https://access.redhat.com/errata/RHSA-2024:6503 | vendor advisory mailing list |
https://access.redhat.com/security/cve/CVE-2024-7341 | vdb entry vendor advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=2302064 | vendor advisory issue tracking |