dbcve.org
SametimeApplication · Hcltech

CVE-2023-45718

HIGH · 7.5 CVSS v3.1 Published 2024-02-09
Fix available
A fix is available. Upgrade to 12.0.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
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.  

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 · moderate confidence

This is a session management vulnerability in HCL Sametime Web clients where sensitive authentication cookies are set persistently and not invalidated upon session closure. The application fails to properly invalidate session cookies, allowing them to remain valid even after users log out or close their sessions, potentially enabling session hijacking or replay attacks.

MitigationImplement proper session invalidation by ensuring cookies are invalidated server-side upon logout/session end, setting appropriate expiration, and clearing cookie values. Additionally, configure cookies with secure attributes (HttpOnly, Secure, SameSite) and ensure session tokens are invalidated server-side.

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
SametimeApplication
Affected:>= 11.5, < 12.0.2

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 installed HCL Sametime version
    Check the Sametime server or client version using the product's built-in version information tool, typically accessible through the administration console or by examining the installed software package details
    Affected if The installed version is 11.5 or later but earlier than 12.0.2
  2. Confirm Web Client component is in use
    Determine whether the Sametime Web Client interface is deployed or accessible to end users, typically accessible via browser to the Sametime server URL
    Affected if The web client is deployed and accessible to users
  3. Inspect authentication cookie configuration
    Log into the Sametime Web Client, perform a session, then log out. Use browser developer tools or a network traffic analyzer to examine authentication-related cookies (such as session or token cookies) before and after logout
    Affected if Authentication cookies remain present or retain valid values after user logs out
  4. Verify session cookie expiration settings
    Examine the cookie attributes (expiration date, domain, path, secure, HttpOnly, SameSite) for authentication session cookies through browser developer tools or by reviewing server-side cookie configuration if accessible
    Affected if Cookies lack proper expiration controls or secure attributes, or cookies persist beyond the session duration

A user is affected if they run Sametime version 11.5 through 12.0.1 with the Web Client enabled and authentication cookies remain valid after session termination.

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
Upgrade available Upgrade to 12.0.2 or later
Fixed in 12.0.2
Interim mitigation

Implement proper session invalidation by ensuring cookies are invalidated server-side upon logout/session end, setting appropriate expiration, and clearing cookie values. Additionally, configure cookies with secure attributes (HttpOnly, Secure, SameSite) and ensure session tokens are invalidated server-side.

Recommended fix Moderate confidence

Sametime 12.0.2 or later

  1. Review HCL Sametime 12.0.2 release notes for upgrade requirements and any prerequisites
  2. Ensure all Sametime server components (web client, proxy, conference, meeting) are compatible with 12.0.2
  3. Perform a complete backup of the current Sametime deployment including configuration and database
  4. Test the upgrade in a non-production environment before deploying to production
  5. Upgrade the Sametime server(s) to version 12.0.2 or later per HCL installation documentation
  6. Verify that session cookies are properly invalidated upon session termination
  7. Confirm the fix by testing user login and logout workflows to ensure cookies no longer persist
Caveat Review HCL compatibility matrix as 12.0.x may have configuration or dependency changes from 11.5.x; some features or integrations may require updates

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

Fix this in Sametime Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45718 — 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-45718 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