CVE-2025-10561
BaseFortify
Publication date: 2025-10-27
Last updated on: 2025-11-11
Assigner: SICK AG
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sick | tloc100-100 | * |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects the SICK TLOC100-100 device, which runs an outdated Ubuntu operating system that is no longer supported. Because the OS is outdated, it may contain known security flaws that attackers could exploit. The vulnerability is critical, with a CVSS score of 9.3, indicating it can be exploited locally without privileges or user interaction, and it can severely impact the device's confidentiality, integrity, and availability. [2]
How can this vulnerability impact me? :
The vulnerability can lead to severe impacts on the affected device, including loss of confidentiality, integrity, and availability. This means attackers could potentially access sensitive information, alter data, or disrupt the device's normal operation. Since the attack vector is local and requires no privileges or user interaction, it poses a significant risk if an attacker gains local access to the device. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
The vulnerability affects the SICK TLOC100-100 device running an outdated Ubuntu operating system that is no longer supported. Detection involves identifying devices running this specific product and verifying the OS version to confirm it is outdated and vulnerable. While no specific detection commands are provided in the resources, general approaches include scanning the network for the SICK TLOC100-100 device (e.g., using network discovery tools) and checking the OS version via device management interfaces or SSH access if available. Since the vulnerability is local with no privileges required, verifying the firmware version against affected versions is also important. For detailed detection and verification, consulting the SICK PSIRT advisories or product documentation is recommended. [2, 1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting device access to trusted entities only and minimizing network exposure of the affected SICK TLOC100-100 device. Applying general security best practices such as those outlined in the 'SICK Operating Guidelines' and the 'ICS-CERT recommended practices on Industrial Security' is advised. Since the device runs an outdated OS, updating or replacing the OS or device firmware when updates become available is recommended. Evaluating the environmental risk individually using CVSS scores is also suggested. No public exploits are known, but proactive access control and network segmentation are key to reducing risk. [2, 4]