Metrics
Affected Vendors & Products
No advisories yet.
Solution
No solution given by the vendor.
Workaround
Please make sure that logs exclude informative level and are stored in a secure way. For more information please follow the official Microsoft Security Considerations document for .NET: https://learn.microsoft.com/en-us/aspnet/core/signalr/security?view=aspnetcore-9.0#access-token-logging Please make sure that only trusted entities have access to the device. Furthermore, you should apply the following General Security Measures when operating the product to mitigate the associated security risk. The collected resources ”SICK Operating Guidelines” and ”ICS-CERT recommended practices on Industrial Security” could help to implement the general security practices.
Thu, 15 Jan 2026 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Certain requests pass the authentication token in the URL as string query parameter, making it vulnerable to theft through server logs, proxy logs and Referer headers, which could allow an attacker to hijack the user's session and gain unauthorized access. | |
| Weaknesses | CWE-598 | |
| References |
|
|
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: SICK AG
Published:
Updated: 2026-01-15T14:52:44.218Z
Reserved: 2026-01-08T09:59:06.199Z
Link: CVE-2026-22644
No data.
Status : Received
Published: 2026-01-15T14:16:28.163
Modified: 2026-01-15T14:16:28.163
Link: CVE-2026-22644
No data.
OpenCVE Enrichment
No data.