CVE-2024-1064
Craftycontrol Crafty Controller 4.0.0 – 4.2.2
Raw vector
CVSS:3.1/AV:N/AC:L/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-1064 is a high-severity Improper Neutralization of HTTP Headers for Scripting Syntax (CWE-644) vulnerability in Craftycontrol Crafty Controller. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked in the top 44% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-16839
Vulnerability Data
A host header injection vulnerability in the HTTP handler component of Crafty Controller allows a remote, unauthenticated attacker to trigger a Denial of Service (DoS) condition via a modified host header
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V4.2.3
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly requires checking/neutralizing untrusted data such as HTTP headers before they reach browser components.
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.
Secure SDLC practices directly require proper output encoding and header sanitization to prevent scripting injection.
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.
Secure development lifecycle mandates input validation and output encoding that directly prevents header-injection flaws.
A.8.26 only requires that security requirements (including resilience against injections) be identified and specified during development; it does not itself neutralize HTTP header syntax or stop exploitation of CWE-644
A.8.27 mandates security-by-design principles (including data validation/sanitization, distrust external input, defense-in-depth, secure architecture reviews against attack patterns) that reach output encoding and header sanitization for this XSS-like weakness in many but not all cases; a bounded remainder exists for non-web or non-HTTP contexts and incomplete application of the principles.
Secure coding standards require proper escaping or rejection of scripting syntax in HTTP headers.
Security testing catches header-injection issues before release, covering most of the weakness.
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-116, a class-level weakness, and none of its children carries one either.