dbcve.org
SametimeApplication · Hcltech

CVE-2024-30122

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 misconfigured security related HTTP headers. It was identified that some HTTP headers were missing on web service responses. This will lead to less secure browser default treatment for the policies controlled by these headers.

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 web service responses are missing security-related HTTP headers (such as X-Frame-Options, X-Content-Type-Options, Content-Security-Policy, or similar). This causes browsers to fall back to less secure default behaviors for security policies, potentially exposing users to clickjacking, MIME-type sniffing, or cross-site scripting risks.

MitigationConfigure the web server or application to include appropriate security HTTP headers on all responses. Headers such as X-Frame-Options, X-Content-Type-Options, Content-Security-Policy, and Strict-Transport-Security should be added and set to secure values.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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 Sametime version
    Locate the Sametime installation directory and check the version information file or use the sametime version command if available. Common locations include /opt/hcl/sametime or the Windows installation path under Program Files.
    Affected if Version is lower than 12.0.2 or exactly 12.0.2 (versions 12.0.0 through 12.0.2 are affected)
  2. Identify Sametime web service endpoint
    Determine the base URL for the Sametime web interface. This is typically accessible on port 8080 or 8443 (HTTPS), or through a configured web server reverse proxy.
    Affected if The web service endpoint is accessible and responds to HTTP requests
  3. Capture HTTP response headers
    Use a tool like curl (curl -I https://your-sametime-server:port), browser DevTools Network tab, or a proxy such as Burp Suite to capture response headers from the Sametime web service.
    Affected if Unable to capture headers indicates the web service may not be running or accessible
  4. Inspect for security headers
    Examine the HTTP response headers for the presence of X-Frame-Options, X-Content-Type-Options, Content-Security-Policy, and Strict-Transport-Security headers.
    Affected if One or more of these security headers are missing from the response

If the installed Sametime version is 12.0.2 or earlier AND the HTTP responses lack security headers such as X-Frame-Options, X-Content-Type-Options, Content-Security-Policy, or Strict-Transport-Security, the environment is affected by this vulnerability.

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

Configure the web server or application to include appropriate security HTTP headers on all responses. Headers such as X-Frame-Options, X-Content-Type-Options, Content-Security-Policy, and Strict-Transport-Security should be added and set to secure values.

Recommended fix Moderate confidence

Sametime 12.0.2 or later

  1. 1. Review the HCL Sametime release notes and documentation on support.hcl-software.com for version 12.0.2 or later
  2. 2. Plan the upgrade ensuring appropriate backup of current configuration and data
  3. 3. Schedule a maintenance window for the upgrade process
  4. 4. Follow HCL upgrade documentation to update Sametime to version 12.0.2 or the latest available version
  5. 5. After upgrade, verify that the HTTP security headers are now present in responses
  6. 6. Test critical Sametime functionality including chat, meetings, and authentication
Caveat Review HCL release notes for any configuration or feature changes between your current version and 12.0.2

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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