Application-state persistence after session termination
Published Apr 22, 2020 · Updated Aug 4, 2024
Insufficient session expiration in JetBrains TeamCity before 2019.2.1 allows attackers to retain application state after logout. JetBrains has not published the affected component or the operation that fails to destroy the application state when a user ends a session. The issue requires an existing user session; public material does not establish whether retained state permits session reuse or only consumes server resources.
Summary
What happened
Insufficient session expiration in JetBrains TeamCity before 2019.2.1 allows attackers to retain application state after logout. JetBrains has not published the affected component or the operation that fails to destroy the application state when a user ends a session. The issue requires an existing user session; public material does not establish whether retained state permits session reuse or only consumes server resources.
The record
- CVE
- CVE-2020-11688
- Published
- Apr 22, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-613
- Attack vector
- network
- Privileges
- Unavailable
Timeline
How it unfolded
- Apr 22, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo