dbcve.org
SametimeApplication · Hcltech

CVE-2023-50355

MEDIUM · 5.3 CVSS v3.1 Published 2024-10-23
Fix available
A fix is available. Upgrade to 12.0.2 or later.
See remediation →
62/100
Remediation priority · Elevated
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
HCL Sametime is impacted by the error messages containing sensitive information. An attacker can use this information to launch another, more focused attack.

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

HCL Sametime contains error handling that exposes sensitive system information in error messages. An unauthenticated attacker could potentially gather intelligence about the underlying system, configuration, or internal structure to launch more targeted follow-on attacks.

MitigationImplement proper error handling that sanitizes error messages, removes stack traces and system details, and returns generic user-friendly messages while logging detailed information server-side for debugging.

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= 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 HCL Sametime installation
    Locate the Sametime installation directory and check for version information files, typically found in the installation root or version.properties file
    Affected if The installed version cannot be determined or is from an older installation method
  2. Determine installed Sametime version
    Read the version file or use the sametime version command if available. Common locations include the installation root directory or check the About dialog in the admin console
    Affected if The exact version number cannot be confirmed from the installation
  3. Compare version against affected range
    Match your installed version against the affected range: versions < 12.0.2 or exactly 12.0.2 are vulnerable
    Affected if Your installed version is either older than 12.0.2 or exactly 12.0.2, indicating you are running a vulnerable version
  4. Inspect error handling configuration
    Review Sametime configuration files for error handling settings, particularly in the web application or proxy configuration files
    Affected if Error handling appears to be configured to return detailed stack traces or system information to users
  5. Verify error message exposure
    Trigger intentional error conditions (such as invalid requests or malformed input) and observe whether returned error messages contain stack traces, file paths, system user names, or internal configuration details
    Affected if Error responses contain sensitive system information such as stack traces, Java class names, file paths, database connection details, or internal server names

You are affected if your HCL Sametime installation is version 12.0.2 or any version prior to 12.0.2, as these versions contain error handling that exposes sensitive system information in error messages.

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 error handling that sanitizes error messages, removes stack traces and system details, and returns generic user-friendly messages while logging detailed information server-side for debugging.

Recommended fix High confidence

Sametime 12.0.2 Fix Pack 1 or later

  1. 1. Review current Sametime deployment version to confirm it is 12.0.2 or earlier
  2. 2. Backup the current Sametime configuration and database
  3. 3. Plan maintenance window for upgrade process
  4. 4. Download HCL Sametime 12.0.2 Fix Pack 1 or later from HCL Support Portal (support.hcl-software.com)
  5. 5. Stop all Sametime services before applying the upgrade
  6. 6. Apply the upgrade following HCL installation documentation
  7. 7. Restart Sametime services after successful installation
  8. 8. Verify that error messages no longer contain sensitive system information
Caveat Review HCL release notes for 12.0.2 FP1 for any configuration changes or deprecated features before upgrading

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

Fix this in Sametime Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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