dbcve.org
Spring SessionFramework / library · VMware

CVE-2023-20866

MEDIUM · 6.5 CVSS v3.1 Published 2023-04-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Spring Session 3.0.0, the HeaderHttpSessionIdResolver writes session IDs to the standard output stream, causing sensitive session identifiers to be exposed in application logs. This information disclosure allows attackers with log access to potentially hijack user sessions.

MitigationUpgrade to a patched version of Spring Session or implement a custom session resolver that does not log session identifiers to stdout.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Spring SessionFramework / library
Affected:= 3.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Spring Session version
    Examine your project's dependency manifest (pom.xml, build.gradle, or the spring-session-core jar manifest) and locate the Spring Session library version. Check if it is exactly 3.0.0.
    Affected if The installed Spring Session version is 3.0.0 exactly.
  2. Locate session resolver configuration
    Search your project configuration files (application.properties, application.yml, or Java configuration classes) for the property spring.session.store-type or any explicit bean definition of HeaderHttpSessionIdResolver.
    Affected if HeaderHttpSessionIdResolver is configured as the session ID resolver.
  3. Review application logs for session identifiers
    Examine standard output and standard error logs from your running application. Search for patterns matching typical session identifiers (long alphanumeric strings, often appearing after headers like 'X-Session-Id:' or 'Session-Id:').
    Affected if Session IDs are being written to stdout/stderr logs.
  4. Check for custom resolver implementation
    Search your codebase for any custom implementations of HttpSessionIdResolver that may log session identifiers, or any logging statements that explicitly output session-related header values.
    Affected if Custom code logs session identifiers to any output stream.

You are affected if your environment uses Spring Session version 3.0.0 with HeaderHttpSessionIdResolver (or a custom resolver that logs session IDs), as this causes session identifiers to appear in application logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to a patched version of Spring Session or implement a custom session resolver that does not log session identifiers to stdout.

Recommended fix High confidence

Spring Session 3.0.1

  1. Upgrade Spring Session from version 3.0.0 to version 3.0.1 in your project's dependency management (Maven pom.xml or Gradle build.gradle)
  2. Rebuild and redeploy the application
  3. Verify that session IDs are no longer being written to standard output logs
  4. Review application logs to confirm no session IDs were previously exposed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Spring Session Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-20866 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-20866 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data