Security readout for executives and security teams
Plain-English summary
CVE-2023-45716 is a low-severity HCL Sametime issue where sensitive information may be passed in a URL. The documented impact is limited confidentiality exposure, not system takeover, data modification, or service disruption.
Executive priority
Treat as a routine remediation item unless affected Sametime systems handle particularly sensitive workflows. It is not currently supported as an emergency patching event by the supplied sources.
Technical view
The issue is mapped to CWE-598 and affects listed HCL Sametime versions. CVSS 3.1 is 1.7 with AV:P/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N, indicating physical access, high complexity, low privilege, user interaction, and limited confidentiality impact.
Likely exposure
Exposure appears limited to organizations running HCL Sametime 11.5, 11.6, 11.6 IF1, 12.0, 12.0 FP1, 12.0.1, or 12.0.1 FP1. The CVE record marks other versions as unaffected by default.
Exploitation context
The source bundle does not show CISA KEV listing, active exploitation, or public exploit evidence. The CVSS vector suggests exploitation is constrained and requires specific conditions, including physical access and user interaction.
Researcher notes
Evidence is sparse beyond the CVE metadata and HCL reference. Validate exposure by version and by whether sensitive data is placed in URLs. Avoid assuming broader products, exploitability, or fixes not named by HCL.
Mitigation direction
- Review HCL advisory KB0109082 for vendor remediation guidance.
- Inventory HCL Sametime deployments and versions.
- Prioritize upgrades or configuration changes named by HCL.
- Limit access to systems where affected Sametime versions remain deployed.
Validation and detection
- Confirm deployed HCL Sametime versions against the affected list.
- Review vendor advisory KB0109082 for fixed or remediated versions.
- Check whether sensitive values appear in Sametime-generated URLs.
- Review URL-retaining logs according to internal privacy policy.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-598: 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 lookupCVE-2023-45716 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 1.7 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:P/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:P/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N0.31.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
1.7LowVector: CVSS:3.1/AV:P/AC:H/PR:L/UI:R/S:U/C:L/I:N/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0109082CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of HTTP Request With Sensitive Query String
Use of HTTP Request With Sensitive Query String represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.