Session hijacking via persistent authentication cookies
Published Feb 9, 2024 · Updated Jun 3, 2025
Insufficient session expiration in HCL Sametime 11.5 through 12.0.1 FP1 allows physically proximate attackers to reuse session cookies. Sametime Web marks sensitive cookie values as persistent and does not invalidate them when the user closes the session. Exploitation requires access to a user's browser cookie after session closure and exposes the still-authenticated session without altering data or service availability.
Summary
What happened
Insufficient session expiration in HCL Sametime 11.5 through 12.0.1 FP1 allows physically proximate attackers to reuse session cookies. Sametime Web marks sensitive cookie values as persistent and does not invalidate them when the user closes the session. Exploitation requires access to a user's browser cookie after session closure and exposes the still-authenticated session without altering data or service availability.
The record
- CVE
- CVE-2023-45718
- Published
- Feb 9, 2024
- Updated
- Jun 3, 2025
- Vendor
- HCL Software
- Product
- HCL Sametime
- Classifications
- CWE-384, CWE-613, T1539
- Attack vector
- physical
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 9, 2024CVE publishedPublication date reported by the CVE source.
- Jun 3, 2025Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=11.5, 11.6, 11.6 IF1, 12.0, 12.0 FP1, 12.0.1, 12.0.1 FP1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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