CVE-2024-10771: SICK InspectorP61x, SICK InspectorP62x and SICK TiM3xx are vulnerable for remote code execution
Due to missing input validation during one step of the firmware update process, the product
is vulnerable to remote code execution. With network access and the user level ”Service”, an attacker
can execute arbitrary system commands in the root user’s contexts.
Security readout for executives and security teams
Plain-English summary
This is a high-impact industrial device issue: an attacker with network access and Service-level privileges could run commands as root during firmware update handling. That creates potential for device takeover, disruption, or data compromise in affected SICK environments.
Executive priority
Treat as priority remediation for industrial environments using affected SICK devices. The risk is serious because compromise can lead to root-level control, but urgency depends on exposure and Service credential control.
Technical view
CVE-2024-10771 is CWE-94 remote code execution caused by missing input validation in one firmware update step. CVSS 3.1 is 8.8, with network attack vector, low complexity, low privileges, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure appears limited to network-reachable affected SICK products where an attacker can obtain or use Service-level access. The bundle lists TDC-X401GL all versions as affected; InspectorP61x, InspectorP62x, and TiM3xx naming is inconsistent with affected-status data.
Exploitation context
The bundle does not show CISA KEV listing or other evidence of active exploitation. Exploitation is not unauthenticated; the attacker needs network access and Service-level privileges, but successful exploitation runs commands in the root context.
Researcher notes
Source data is partly inconsistent: the title names InspectorP61x, InspectorP62x, and TiM3xx, while the affected list marks TDC-X401GL all versions affected and shows version 0/default unaffected for the named product families. Validate against SICK’s CSAF before scoping.
Mitigation direction
Check SICK PSIRT and advisory SCA-2024-0006 for official fixes or mitigations.
Apply vendor-provided firmware or configuration guidance where available.
Restrict management and firmware update interfaces to trusted administrative networks.
Limit and audit Service-level credentials on affected devices.
Apply CISA ICS network segmentation and remote-access hardening practices.
Validation and detection
Inventory SICK devices and confirm model, firmware, and deployment location.
Compare assets against SICK CSAF advisory SCA-2024-0006.
Verify affected devices are not reachable from untrusted networks.
Review who has Service-level access and remove unnecessary accounts.
Check device logs for unusual firmware update or administrative activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-94: Code execution behavior lookup
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
7Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9SICK AG
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-94 · source CWE mapping
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.