dbcve.org
SametimeApplication · Hcltech

CVE-2023-50349

HIGH · 8.8 CVSS v3.1 Published 2024-02-09
Fix available
A fix is available. Upgrade to 12.0.2 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 Cross Site Request Forgery (CSRF) vulnerability. Some REST APIs in the Sametime Proxy application can allow an attacker to perform malicious actions on the application.

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

Cross-Site Request Forgery (CSRF) vulnerability in IBM HCL Sametime's Proxy application allows attackers to trick authenticated users into making unintended requests to vulnerable REST APIs. Since the attack exploits the trust a site has in a user's browser, successful exploitation can lead to unauthorized actions being performed on behalf of legitimate users.

MitigationImplement anti-CSRF tokens (synchronizer token pattern) for all state-changing REST API endpoints in the Sametime Proxy application, and configure SameSite cookie attributes along with proper Origin/Referer header validation.

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:< 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Determine installed HCL Sametime version
    Locate the Sametime installation directory and find the version file. On Linux/Unix systems, check /opt/hcl/sametime/version or similar. On Windows, inspect the installation folder for a version.txt or about file. Alternatively, access the Sametime administration console and view the product version information.
    Affected if Installed version is lower than 12.0.2
  2. Confirm Sametime Proxy application is in use
    Identify whether the Sametime Proxy component is deployed and active. This is typically found in the web application server (such as WebSphere) where Sametime is hosted. Check the application deployment configuration or administration console for a proxy or stproxy application.
    Affected if Proxy application is deployed and version is below 12.0.2
  3. Inspect REST API endpoints for CSRF protection
    Review the REST API endpoints exposed by the Proxy application. Examine API configuration files or source code to determine if synchronizer token pattern (anti-CSRF tokens) is implemented for state-changing endpoints such as user settings, messaging, or administrative functions.
    Affected if State-changing REST API endpoints lack anti-CSRF token implementation

Environment is affected if HCL Sametime with the Proxy application is deployed and the installed version is below 12.0.2 without anti-CSRF token protection on REST APIs.

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 anti-CSRF tokens (synchronizer token pattern) for all state-changing REST API endpoints in the Sametime Proxy application, and configure SameSite cookie attributes along with proper Origin/Referer header validation.

Recommended fix High confidence

HCL Sametime 12.0.2

  1. 1. Back up the current Sametime installation and database before proceeding with any upgrade.
  2. 2. Download HCL Sametime version 12.0.2 from the official HCL Support Portal (support.hcltechsw.com).
  3. 3. Review the HCL Sametime 12.0.2 installation and upgrade documentation for prerequisite steps.
  4. 4. Stop the Sametime services.
  5. 5. Install or upgrade to Sametime 12.0.2 following the official upgrade procedures.
  6. 6. Restart the Sametime services.
  7. 7. Verify the REST APIs in the Sametime Proxy application are functioning correctly.
  8. 8. Confirm the CSRF vulnerability is remediated by testing that the vulnerable REST endpoints now properly validate anti-CSRF tokens.
Caveat Review HCL Sametime 12.0.2 release notes for any configuration or feature changes that may affect your deployment

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

Fix this in Sametime Scoped from the published advisory
  • Consultation6.0 h
  • Implementation20.0 h
  • Testing10.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,020
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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