LiveActive security incident?Get immediate response
CVE Record

CVE-2023-45718: HCL Sametime is impacted by a failure to invalidate sessions

Sametime is impacted by a failure to invalidate sessions. The application is setting sensitive cookie values in a persistent manner in Sametime Web clients. When this happens, cookie values can remain valid even after a user has closed out their session.

LowCVSS 3.9Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

HCL Sametime web clients may keep sensitive session cookie values persistent. If someone can access a user’s device after the user closes the session, those cookies may still be valid. The main business risk is unauthorized access to Sametime content, but the published score rates this low because exploitation requires physical access and user interaction.

Executive priority

Treat this as a low-severity but privacy-relevant session management issue. It is not a broad remote compromise based on the supplied evidence, but organizations using affected Sametime versions should remediate according to HCL guidance, especially where shared or physically accessible endpoints exist.

Technical view

CVE-2023-45718 is a CWE-613 session expiration weakness in HCL Sametime. Sensitive cookie values are set persistently in Sametime Web clients and may remain valid after the user closes the session. Affected versions listed are 11.5, 11.6, 11.6 IF1, 12.0, 12.0 FP1, 12.0.1, and 12.0.1 FP1.

Likely exposure

Exposure is limited to organizations using affected HCL Sametime Web client versions. The CVSS vector indicates local physical access, high attack complexity, low privileges, and required user interaction, so shared workstations, kiosks, unmanaged endpoints, or poor session hygiene are the most relevant scenarios.

Exploitation context

The provided sources do not report active exploitation, and CISA KEV status is false. The published vector suggests opportunistic abuse is constrained because an attacker needs physical access and user interaction. The highest concern is post-session access on a device where valid persistent cookies remain available.

Researcher notes

Evidence is limited to the CVE record, CVE List entry, and HCL advisory reference. No exploit code, active exploitation, or detailed fix text is included in the supplied bundle. The assessment relies on the published CVSS vector and affected version list.

Mitigation direction

  • Review HCL advisory KB0109082 for fixed versions or vendor-approved configuration guidance.
  • Prioritize remediation for shared devices, kiosks, and unmanaged endpoints using Sametime Web clients.
  • Enforce endpoint lock, logout, and browser data-clearing policies for shared systems.
  • Inventory affected Sametime versions and plan updates according to HCL guidance.

Validation and detection

  • Confirm whether deployed Sametime versions match the affected version list.
  • Review Sametime Web session cookie persistence and expiration behavior in a controlled test environment.
  • Check whether browser close or logout invalidates session state as expected.
  • Verify shared-device controls prevent reuse of previous user sessions.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-613: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2023-45718 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.9 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.9CVSS 3.1LowCVSS:3.1/AV:P/AC:H/PR:L/UI:R/S:U/C:H/I:N/A:N0.33.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.9Low
CVSS 3.1 vector shape for CVE-2023-45718Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HCL SoftwareHCL Sametime11.5, 11.6, 11.6 IF1, 12.0, 12.0 FP1, 12.0.1, 12.0.1 FP1unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-613 · source CWE mapping

Insufficient Session Expiration

Insufficient Session Expiration represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.