UpdateService crash via absent or delayed response
Published Oct 27, 2025 · Updated Oct 27, 2025
An uncaught exception in SICK TLOC100-100 all firmware versions allows remote attackers to crash UpdateService during file transfers. A tampered C++ CLI client delays or omits the response expected by UpdateService, leaving the transfer path's exception unhandled and terminating the service. The attacker must reach the device from an adjacent network and manipulate the client during a transfer; the crash interrupts updates and device availability.
Summary
What happened
An uncaught exception in SICK TLOC100-100 all firmware versions allows remote attackers to crash UpdateService during file transfers. A tampered C++ CLI client delays or omits the response expected by UpdateService, leaving the transfer path's exception unhandled and terminating the service. The attacker must reach the device from an adjacent network and manipulate the client during a transfer; the crash interrupts updates and device availability.
The record
- CVE
- CVE-2025-59462
- Published
- Oct 27, 2025
- Updated
- Oct 27, 2025
- Vendor
- SICK AG
- Product
- TLOC100-100
- Classifications
- CWE-248, T1499.004
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 27, 2025CVE publishedPublication date reported by the CVE source.
- Oct 27, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=all versions
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo