Persistent service interruption via uncontrolled resource consumption
Published Oct 27, 2025 · Updated Oct 27, 2025
Resource exhaustion in SICK AG TLOC100-100 firmware before 7.1.1 allows local users with SSH access to persistently interrupt services. SICK identifies uncontrolled resource consumption but has not published the affected service, resource type, request path, or operation that omits limits or throttling. An unprivileged SSH account is required, and exhaustion can disable SSH itself and leave device services persistently unavailable.
Summary
What happened
Resource exhaustion in SICK AG TLOC100-100 firmware before 7.1.1 allows local users with SSH access to persistently interrupt services. SICK identifies uncontrolled resource consumption but has not published the affected service, resource type, request path, or operation that omits limits or throttling. An unprivileged SSH account is required, and exhaustion can disable SSH itself and leave device services persistently unavailable.
The record
- CVE
- CVE-2025-59459
- Published
- Oct 27, 2025
- Updated
- Oct 27, 2025
- Vendor
- SICK AG
- Product
- Triton Floor-LOC TLOC100-100
- Classifications
- CWE-770, T1499.004
- Attack vector
- local
- Privileges
- authenticated
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=0 <<7.1.1
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.
Weakness, pattern, technique
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