CVE-2024-0788
Realdefen Superantispyware 10.0.1260
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:HSummary
CVE-2024-0788 is a medium-severity Static Code Injection (CWE-96) vulnerability in Realdefen Superantispyware. Its CVSS base score is 6.6 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 15th 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 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-16576
Vulnerability Data
SUPERAntiSpyware Pro X v10.0.1260 is vulnerable to kernel-level API parameters manipulation and Denial of Service vulnerabilities by triggering the 0x9C402140 IOCTL code of the saskutil64.sys driver.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.2
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover missing neutralization of directives in saved code artifacts.
Input validation directly stops unneutralized directives from being inserted into static code resources.
Engineering principles include secure input handling and neutralization requirements that structurally avoid static injection.
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 input neutralization to block static code injection into templates, configs, or libraries.
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.
Security testing in development and acceptance will detect static code injection but does not prevent it at the source.
Secure development life cycle mandates input validation and sanitization that directly prevents static code injection.
Application security requirements include rules for neutralizing untrusted input before it is stored in executable resources.
Secure architecture principles reduce injection surfaces but do not prescribe the specific neutralization techniques.
Secure coding explicitly requires proper neutralization of directives in templates, libraries and configuration files.
Change management can catch unsafe code changes but does not enforce input neutralization.