Skip to content
OpenAdvisories

Weakness (CWE)

CWE-384: Session Fixation

Compound Incomplete

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.

More detail

Such a scenario is commonly observed when:

- A web application authenticates a user without first invalidating the existing session, thereby continuing to use the session already associated with the user.

- An attacker is able to force a known session identifier on a user so that, once the user authenticates, the attacker has access to the authenticated session.

- The application or container uses predictable session identifiers.

In the generic exploit of session fixation vulnerabilities, an attacker creates a new session on a web application and records the associated session identifier. The attacker then causes the victim to associate, and possibly authenticate, against the server using that session identifier, giving the attacker access to the user's account through the active session.

How to prevent it (3 mitigations)
  1. Architecture and Design

    Invalidate any existing session identifiers prior to authorizing a new user session.

  2. Architecture and Design

    For platforms such as ASP that do not generate new values for sessionid cookies, utilize a secondary cookie. In this approach, set a secondary cookie on the user's browser to a random value and set a session variable to the same value. If the session variable and the cookie value ever don't match, invalidate the session, and force the user to log on again.

  3. Operation

    Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].

Source: MITRE CWE-384

144 results · Clear filters · Feed

  • Medium 6.5

    Keycloak: session hijacking via re-authentication

    A flaw was found in Keycloak that occurs from an error in the re-authentication mechanism within org.keycloak.authentication. This flaw allows hijacking an active Keycloak session by triggering a new authentication process with the query parameter "prompt=log…

  • Medium 4.2

    Session Fixation Vulnerability in zenml-io/zenml

    A session fixation vulnerability exists in the zenml-io/zenml application, where JWT tokens used for user authentication are not invalidated upon logout. This flaw allows an attacker to bypass authentication mechanisms by reusing a victim's JWT token.

  • Medium 5.9

    Contao's remember-me tokens will not be cleared after a password change

    Contao is an open source content management system. Prior to version 4.13.40, when a frontend member changes their password in the personal data or the password lost module, the corresponding remember-me tokens are not removed. If someone compromises an accou…

  • Medium 5.9

    Clients removed during unpairing process may regain access if Sunshine was not restarted

    Sunshine is a self-hosted game stream host for Moonlight. Starting in version 0.10.0 and prior to version 0.23.0, after unpairing all devices in the web UI interface and then pairing only one device, all of the previously devices will be temporarily paired. V…

  • Medium 4.3

    Bdtask Wholesale Inventory Management System session fixiation

    A vulnerability was found in Bdtask Wholesale Inventory Management System up to 20240311. It has been declared as problematic. Affected by this vulnerability is an unknown functionality. The manipulation leads to session fixiation. The attack can be launched …

  • Medium 6.5

    Apache DolphinScheduler: Session do not expire after password change

    Session Fixation Apache DolphinScheduler before version 3.2.0, which session is still valid after the password change. Users are recommended to upgrade to version 3.2.1, which fixes this issue.

  • Medium 5.4

    Liferay Portal's account lockout does not invalidate existing user sessions

    Account lockout in Liferay Portal 7.2.0 through 7.3.0, and older unsupported versions, and Liferay DXP 7.2 before fix pack 5, and older unsupported versions does not invalidate existing user sessions, which allows remote authenticated users to remain authenti…

  • Medium 5.7

    graylog2-server Session Fixation vulnerability through cookie injection

    Graylog is a free and open log management platform. Starting in version 4.3.0 and prior to versions 5.1.11 and 5.2.4, reauthenticating with an existing session cookie would re-use that session id, even if for different user credentials. In this case, the pre-…

  • Medium 6.3

    IBM PowerSC session fixation

    IBM PowerSC 1.3, 2.0, and 2.1 does not provide logout functionality, which could allow an authenticated user to gain access to an unauthorized user using session fixation. IBM X-Force ID: 275131.

  • Medium 5.5

    An issue was discovered on GL.iNet devices before version 4.5.0. They assign the same session ID after each user reboot…

  • Medium 6.7

    Uptime Kuma Password Change Vulnerability

    Uptime Kuma is an easy-to-use self-hosted monitoring tool. Prior to version 1.23.9, when a user changes their login password in Uptime Kuma, a previously logged-in user retains access without being logged out. This behavior persists consistently, even after s…

  • Medium 6.5

    Symfony possible session fixation vulnerability

    Symfony is a PHP framework for web and console applications and a set of reusable PHP components. Starting in versions 5.4.21 and 6.2.7 and prior to versions 5.4.31 and 6.3.8, `SessionStrategyListener` does not migrate the session after every successful login…

  • Medium 6.8

    Broken Session Management in Puppet Enterprise

    Versions of Puppet Enterprise prior to 2021.7.6 and 2023.5 contain a flaw which results in broken session management for SAML implementations.

  • Medium 6.7

    Uptime Kuma has Persistentent User Sessions

    Uptime Kuma is a self-hosted monitoring tool. Prior to version 1.23.3, attackers with access to a user's device can gain persistent account access. This is caused by missing verification of Session Tokens after password changes and/or elapsed inactivity perio…

  • Medium 6.8

    Keycloak: session takeover with oidc offline refreshtokens

    A flaw was found in the offline_access scope in Keycloak. This issue would affect users of shared computers more (especially if cookies are not cleared), due to a lack of root session validation, and the reuse of session ids across root and user authenticatio…

  • Medium 6.4

    Potential Predictable Session ID

    Session Fixation vulnerability in Honeywell PM43 on 32 bit, ARM (Printer web page modules) allows Session Credential Falsification through Prediction.This issue affects PM43 versions prior to P10.19.050004. Update to the latest available firmware version of t…

  • Medium 4.3

    Session Fixation in instantsoft/icms2

    Session Fixation in GitHub repository instantsoft/icms2 prior to 2.16.1.

  • Medium 6.8

    Session Fixation in fossbilling/fossbilling

    Session Fixation in GitHub repository fossbilling/fossbilling prior to 0.5.1.

  • Medium 4.2

    Session Fixation in froxlor/froxlor

    Session Fixation in GitHub repository froxlor/froxlor prior to 2.1.0.

  • Medium 5.4

    Jenkins WSO2 Oauth Plugin Session Fixation vulnerability

    Jenkins WSO2 Oauth Plugin 1.0 and earlier does not invalidate the previous session on login.

  • Medium 6.5

    Cross site request forgery token fixation in fastify-passport

    @fastify/passport is a port of passport authentication library for the Fastify ecosystem. The CSRF (Cross-Site Request Forger) protection enforced by the `@fastify/csrf-protection` library, when combined with `@fastify/passport` in affected versions, can be b…

  • Medium 5.4

    Session Fixation in alextselegidis/easyappointments

    Session Fixation in GitHub repository alextselegidis/easyappointments prior to 1.5.0.

  • Medium 5.4

    OXID eShop 6.2.x before 6.4.4 and 6.5.x before 6.5.2 allows session hijacking, leading to partial access of a customer'…

  • Medium 6.3

    Symfony vulnerable to Session Fixation of CSRF tokens

    Symfony is a PHP framework for web and console applications and a set of reusable PHP components. When authenticating users Symfony by default regenerates the session ID upon login, but preserves the rest of session attributes. Because this does not clear CSR…

  • Medium 6.3

    kassi xingwall oauth.js session fixiation

    A vulnerability, which was classified as critical, has been found in kassi xingwall. This issue affects some unknown processing of the file app/controllers/oauth.js. The manipulation leads to session fixiation. The patch is named e9f0d509e1408743048e29d9c099d…

  • Medium 4.6

    A vulnerability in the web-based management interface of Aruba EdgeConnect Enterprise Orchestrator could allow an remot…

  • Medium 6.1

    Nortek Linear eMerge E3-Series 0.32-08f, 0.32-07p, 0.32-07e, 0.32-09c, 0.32-09b, 0.32-09a, and 0.32-08e were discovered…

  • Medium 4.2

    Tribal Systems Zenario CMS Remember Me session fixiation

    A vulnerability, which was classified as problematic, has been found in Tribal Systems Zenario CMS 9.3.57595. This issue affects some unknown processing of the component Remember Me Handler. The manipulation leads to session fixiation. The attack may be initi…

  • Medium 6.5

    An issue was discovered in Appalti & Contratti 9.12.2. It allows Session Fixation. When a user logs in providing a JSES…

  • Medium 4.6

    Session fixation exists in ZoneMinder through 1.36.12 as an attacker can poison a session cookie to the next logged-in …

  • Medium 5.4

    Concrete CMS vulnerable to Session Fixation

    Concrete CMS (formerly concrete5) below 8.5.10 and between 9.0.0 and 9.1.2 does not issue a new session ID upon successful OAuth authentication. Remediate by updating to Concrete CMS 9.1.3+ or 8.5.10+.

  • Medium 5.8

    Session Fixation and Insufficient Session Expiration

    Session fixation and insufficient session expiration vulnerabilities allow an attacker to perfom session hijacking attacks against users. This issue affects: Lanner Inc IAC-AST2500A standard firmware version 1.10.0.

  • Medium 6.5

    Improper Session Management Vulnerability in Tacitine Firewall

    This vulnerability exists in Tacitine Firewall, all versions of EN6200-PRIME QUAD-35 and EN6200-PRIME QUAD-100 between 19.1.1 to 22.20.1 (inclusive), due to improper session management in the Tacitine Firewall web-based management interface. An unauthenticate…

  • Medium 6.4

    Session Fixation in ikus060/rdiffweb

    Session Fixation in GitHub repository ikus060/rdiffweb prior to 2.4.7.

  • Medium 4.6

    Session Fixation in snipe/snipe-it

    Session Fixation in GitHub repository snipe/snipe-it prior to 6.0.10.

  • Medium 5.4

    Dell Wyse Management Suite 3.6.1 and below contains a Session Fixation vulnerability. A unauthenticated attacker could …

  • Medium 4.8

    Session Fixation

    This affects the package passport before 0.6.0. When a user logs in or logs out, the session is regenerated instead of being closed.

  • Medium 6.5

    Hybridsessions does not expire session id on logout

    Silverstripe silverstripe/framework through 4.10 allows Session Fixation.

  • Medium 4.3

    Session Fixation in filegator/filegator

    Session Fixation in GitHub repository filegator/filegator prior to 7.8.0.

  • Medium 6.5

    B. Braun SpaceCom, Battery Pack SP with Wi-Fi, and Data module compactplus

    A session fixation vulnerability in the B. Braun Melsungen AG SpaceCom administrative interface Version L81/U61 and earlier, and the Data module compactplus Versions A10 and A11 allows remote attackers to hijack web sessions and escalate privileges.