CVE-2024-24257
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-24257 is a high-severity Special Element Injection (CWE-75) vulnerability in Github (inferred from references). Its CVSS base score is 7.5 (High).
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 SI-10 (Information Input Validation) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-21681
Vulnerability Data
An issue in skteco.com Central Control Attendance Machine web management platform v.3.0 allows an attacker to obtain sensitive information via a crafted script to the csl/user component.
- CWE(s)
Related Threats
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly stops special-element injection by rejecting or sanitizing untrusted data before it reaches a different control plane.
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.
Logging can record injection attempts for detection but does not prevent the weakness.
A.8.25 mandates secure SDLC practices including secure coding guidelines, security requirements, checkpoints, testing (scans/penetration), and developer training that reach special-element injection in the development phase, but leaves a bounded remainder (e.g. outsourced development without full assurance per 8.30, incomplete enforcement of guidelines across all languages/projects, or post-development injection vectors).
Application security requirements explicitly call for controls against injection flaws including special-element handling.
A.8.27 mandates security engineering principles including data validation/sanitization, distrust external input, security by design, and design reviews against attack patterns; this directly stops special-element injection from being exploitable in most cases, with a bounded remainder in incomplete implementation or novel attack patterns.
Secure coding standards require rigorous input sanitization, directly eliminating CWE-75.
Security testing catches injection vulnerabilities but does not itself implement the sanitization fix.
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-75, a class-level weakness, and none of its children carries one either.