Sametime
by HCLTech
CVEs (11)
| CVE | Vendor / Product | Sev | Risk | CVSS | EPSS | KEV | Published | Description |
|---|---|---|---|---|---|---|---|---|
| CVE-2026-21791 | Low | 0.21 | 3.3 | 0.00 | Mar 10, 2026 | HCL Sametime for Android is impacted by a sensitive information disclosure. Hostnames information is written in application logs and certain URL | ||
| CVE-2025-31966 | Low | 0.18 | 2.7 | 0.00 | Mar 17, 2026 | HCL Sametime is vulnerable to broken server-side validation. While the application performs client-side input checks, these are not enforced by the web server. An attacker can bypass these restrictions by sending manipulated HTTP requests directly to the server. | ||
| CVE-2023-50355 | 0.00 | — | 0.00 | Oct 23, 2024 | HCL Sametime is impacted by the error messages containing sensitive information. An attacker can use this information to launch another, more focused attack. | |||
| CVE-2024-30124 | 0.00 | — | 0.00 | Oct 23, 2024 | HCL Sametime is impacted by insecure services in-use on the UIM client by default. An unused legacy REST service was enabled by default using the HTTP protocol. An attacker could potentially use this service endpoint maliciously. | |||
| CVE-2024-30122 | 0.00 | — | 0.00 | Oct 23, 2024 | 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. | |||
| CVE-2023-45696 | 0.00 | — | 0.00 | Feb 10, 2024 | Sametime is impacted by sensitive fields with autocomplete enabled in the Legacy web chat client. By default, this allows user entered data to be stored by the browser. | |||
| CVE-2023-45716 | 0.00 | — | 0.00 | Feb 9, 2024 | Sametime is impacted by sensitive information passed in URL. | |||
| CVE-2023-50349 | 0.00 | — | 0.00 | Feb 9, 2024 | 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. | |||
| CVE-2022-42446 | 0.00 | — | 0.00 | Nov 30, 2022 | Starting with Sametime 12, anonymous users are enabled by default. After logging in as an anonymous user, one has the ability to browse the User Directory and potentially create chats with internal users. | |||
| CVE-2021-27771 | 0.00 | — | 0.01 | May 12, 2022 | User SID can be modified resulting in an Arbitrary File Upload or deletion of directories causing a Denial of Service. When interacting in a normal matter with the Sametime chat application, users hold a cookie containing their session ID (SID). This value is also used when… | |||
| CVE-2021-27755 | 0.00 | — | 0.00 | Feb 21, 2022 | "Sametime Android potential path traversal vulnerability when using File class" |
- risk 0.21cvss 3.3epss 0.00
HCL Sametime for Android is impacted by a sensitive information disclosure. Hostnames information is written in application logs and certain URL
- risk 0.18cvss 2.7epss 0.00
HCL Sametime is vulnerable to broken server-side validation. While the application performs client-side input checks, these are not enforced by the web server. An attacker can bypass these restrictions by sending manipulated HTTP requests directly to the server.
- CVE-2023-50355Oct 23, 2024risk 0.00cvss —epss 0.00
HCL Sametime is impacted by the error messages containing sensitive information. An attacker can use this information to launch another, more focused attack.
- CVE-2024-30124Oct 23, 2024risk 0.00cvss —epss 0.00
HCL Sametime is impacted by insecure services in-use on the UIM client by default. An unused legacy REST service was enabled by default using the HTTP protocol. An attacker could potentially use this service endpoint maliciously.
- CVE-2024-30122Oct 23, 2024risk 0.00cvss —epss 0.00
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.
- CVE-2023-45696Feb 10, 2024risk 0.00cvss —epss 0.00
Sametime is impacted by sensitive fields with autocomplete enabled in the Legacy web chat client. By default, this allows user entered data to be stored by the browser.
- CVE-2023-45716Feb 9, 2024risk 0.00cvss —epss 0.00
Sametime is impacted by sensitive information passed in URL.
- CVE-2023-50349Feb 9, 2024risk 0.00cvss —epss 0.00
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.
- CVE-2022-42446Nov 30, 2022risk 0.00cvss —epss 0.00
Starting with Sametime 12, anonymous users are enabled by default. After logging in as an anonymous user, one has the ability to browse the User Directory and potentially create chats with internal users.
- CVE-2021-27771May 12, 2022risk 0.00cvss —epss 0.01
User SID can be modified resulting in an Arbitrary File Upload or deletion of directories causing a Denial of Service. When interacting in a normal matter with the Sametime chat application, users hold a cookie containing their session ID (SID). This value is also used when…
- CVE-2021-27755Feb 21, 2022risk 0.00cvss —epss 0.00
"Sametime Android potential path traversal vulnerability when using File class"