# Cwe 613 Insufficient Session Expiration

> Use this skill when you need to remediate CWE-613 (Insufficient Session Expiration) vulnerabilities in Java code. Triggers on SAST findings, security reviews, or when fixing insufficient session expiration issues.

- Skill: `developerscoffee/cwe-613-insufficient-session-expiration` (Agent Skill)
- Install (CLI): `npx skillmds@latest add developerscoffee/cwe-613-insufficient-session-expiration`
- Raw SKILL.md: https://api.skillmd.com/api/skills/developerscoffee/cwe-613-insufficient-session-expiration/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Security
- License: MIT
- Author: DevelopersCoffee (https://skillmd.com/u/developerscoffee)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/developerscoffee/cwe-613-insufficient-session-expiration

---


# CWE-613 Insufficient Session Expiration

## Description

Insufficient Session Expiration

Reference:
https://cwe.mitre.org/data/definitions/613.html


**OWASP Category**: A07:2021 – Identification and Authentication Failures


---

## Vulnerable Pattern


### ❌ Example 1: Vulnerable Pattern

```java
// VULNERABLE: No session timeout configured
@Configuration
public class SecurityConfig {
    // No session management configured
}
```


**Why it's vulnerable:** This pattern is vulnerable to Insufficient Session Expiration




---

## Deterministic Fix


### ✅ Secure Implementation: Secure Implementation

```java
// SECURE: Configure session timeout and management
@Configuration
@EnableWebSecurity
public class SecurityConfig {
    @Bean
    public SecurityFilterChain filterChain(HttpSecurity http) throws Exception {
        http.sessionManagement(session -> session
            .sessionCreationPolicy(SessionCreationPolicy.IF_REQUIRED)
            .maximumSessions(1)
            .expiredUrl("/session-expired")
        );
        return http.build();
    }
}
// In application.properties:
// server.servlet.session.timeout=30m
```


**Why it's secure:** Implements proper protection against Insufficient Session Expiration




---

## Detection Pattern

Look for these patterns in your codebase:


```bash
# Find session configuration
grep -rn "sessionManagement\\|session.timeout" --include="*.java" --include="*.properties"
```



---

## Remediation Steps


1. Set appropriate session timeout (15-30 minutes for sensitive apps)

2. Invalidate session on logout

3. Limit concurrent sessions

4. Re-authenticate for sensitive operations


---

## Key Imports

```java

import org.springframework.security.config.annotation.web.configuration.EnableWebSecurity;

import org.springframework.security.config.http.SessionCreationPolicy;

```

---

## Verification

After remediation:


- Run SAST scanner to confirm vulnerability is resolved

- Review all instances of the vulnerable pattern

- Add unit tests that verify the secure implementation

- Check for similar patterns in related code


---

## Trigger Examples

```
Fix CWE-613 vulnerability
Resolve Insufficient Session Expiration issue
Secure this Java code against insufficient session expiration
SAST reports CWE-613
```

---

## Common Vulnerable Locations

| Layer | Files | Patterns |
|-------|-------|----------|

| Controller | `*Controller.java` | User input handling |

| Service | `*Service.java` | Business logic |

| Repository | `*Repository.java` | Data access |


---

## References


- [CWE-613: Insufficient Session Expiration](https://cwe.mitre.org/data/definitions/613.html)


---

**Source**: Generated by [Java CWE Security Skills Generator](https://github.com/DevelopersCoffee/java-cwe-security-skills)
**Last Updated**: 2026-03-07