CVE-2024-22815
Tormach Pathpilot Controller 2.9.6
Raw vector
CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-22815 is a medium-severity Improper Handling of Syntactically Invalid Structure (CWE-228) vulnerability in Tormach Pathpilot Controller. Its CVSS base score is 5.3 (Medium).
Operationally, ranked at the 12th 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 SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-20345
Vulnerability Data
An issue in the communication protocol of Tormach xsTECH CNC Router, PathPilot Controller v2.9.6 allows attackers to cause a Denial of Service (DoS) via crafted commands.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
SI-10 requires validity checks on information inputs, directly stopping syntactically malformed data from being processed without proper handling.
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.25 mandates secure SDLC practices (secure coding guidelines, security requirements, checkpoints, testing including code scans) that reach improper syntactic handling during development; this prevents exploitation for many cases but leaves a bounded remainder (e.g. non-code-structure inputs, runtime parsers, or incomplete guideline application)
Application security requirements include explicit rules for input validation and malformed-data handling.
A.8.27 mandates security-by-design principles including data validation/sanitization, distrust-external-input, secure architecture reviews against attack patterns, and zero-trust verification; this reaches a minority slice of CWE-228 (invalid structure in external inputs) but leaves most instances (e.g. internal malformed data, non-input structures, parser differentials) unaddressed as the clause sets process rather than mandating complete syntactic enforcement everywhere.
Secure coding explicitly requires validation of all input syntax and structure, directly eliminating CWE-228.
Security testing can detect malformed-input issues but does not itself implement the handling logic.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-228, a class-level weakness, and none of its children carries one either.