Insufficient Session Expiration

Opis

According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

Skutki

• Access Control

  Bypass Protection Mechanism

Zapobieganie

• Implementation

  Set sessions/credentials expiration date.

Przykłady podatności

• CVE-2025-46344 JavaScript SDK does not set an expiration time for JWE tokens related to a session
• CVE-2024-8888 Web interface for a power quality analyzer uses tokens without an expiration date
• CVE-2024-35206 network traffic analyzer for PROFINET networks does not expire sessions
• CVE-2024-27782 AI/ML monitor for IT operations allows re-use of old session tokens due to insufficient session expiration

Słabość nadrzędna

• CWE-672 Operation on a Resource after Expiration or Release

Może prowadzić do

• CWE-287 Improper Authentication

Kiedy powstaje

• Architecture and Design
• Implementation — REALIZATION: This weakness is caused during implementation of an architectural security tactic.

Dotyczy

Not Language-Specific, Web Based, Web Server

Uwagi

This CWE entry is being considered for deprecation. For many years (as of CWE 4.20), the intention and usage of this CWE entry has evolved to include many notions of "sessions" that are not specific to the web. The scope of this entry could be expanded accordingly, or it could be split into multiple separate entries. The original WASC-47 entry [REF-1520] includes considerations forcing re-authentication for "inactivity" (expiring sessions after a period of inactivity) versus "absolute" (a fixed expiration time), with a goal to "keep the lifespan of a session ID as short as possible." However, this CWE has also been used for situations in which a session is not fully invalidated or terminated upon logout, which is a different weakness than the original intention for this entry; however, as of CWE 4.19.1, there is no entry that covers this other variation. There is also evidence that this CWE entry is used for session fixation (CWE-384).

The lack of proper session expiration may improve the likely success of certain attacks. For example, an attacker may intercept a session ID, possibly via a network sniffer or Cross-site Scripting attack. Although short session expiration times do not help if a stolen token is immediately used, they will protect against ongoing replaying of the session ID. In another scenario, a user might access a web site from a shared computer (such as at a library, Internet cafe, or open work environment). Insufficient Session Expiration could allow an attacker to use the browser's back button to access web pages previously accessed by the victim.

Źródła

1. Insufficient Session Expiration — WASC