Cyber Resilience

CVE-2025-59463

Sick Tloc100-100 Firmware

Published
27 October 2025
Modified
03 November 2025
Patch / advisory
View advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
EPSS Score 0.0038 31th percentile
Risk Priority 37 floored blend · peak EPSS

Summary

CVE-2025-59463 is a medium-severity Deadlock (CWE-833) vulnerability in Sick Tloc100-100 Firmware. Its CVSS base score is 4.3 (Medium).

Operationally, ranked at the 31th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

An attacker may cause chunk-size mismatches that block file transfers and prevent subsequent transfers.

CWE(s)
CWE-833

Related Threats

CVEs Like This One

CVE-2025-59459Same product: Sick Tloc100-100
CVE-2025-59462Same product: Sick Tloc100-100
CVE-2025-59461Same product: Sick Tloc100-100
CVE-2025-59460Same product: Sick Tloc100-100
CVE-2023-4420Same vendor: Sick
CVE-2025-49200Same vendor: Sick
CVE-2023-43700Same vendor: Sick
CVE-2023-5288Same vendor: Sick
CVE-2023-31411Same vendor: Sick
CVE-2023-35698Same vendor: Sick

Affected Assets

sick
tloc100-100 firmware
all versions

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.4.3

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation activities can exercise concurrent paths and resource contention to discover deadlock conditions before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles applied during design can incorporate synchronization ordering, timeouts, and resource hierarchies that structurally avoid deadlock formation.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
prevents

Secure SDLC practices can include concurrency analysis and lock discipline to avoid deadlock conditions.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect deadlock conditions through stress and concurrency testing.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle requires deadlock analysis and avoidance techniques during design and coding.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure system architecture principles include concurrency controls and resource-locking discipline that prevent deadlock.

A.8.28 Secure coding partial match
prevents

Secure coding standards mandate safe lock ordering, timeouts, and deadlock detection patterns.

A.8.32 Change management none match
none

Change management may catch deadlock-related defects during reviews but does not directly address concurrency design.

References