CVE-2024-31806
Totolink Ex200 Firmware 4.0.3c.7646_b20201211
Raw vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HSummary
CVE-2024-31806 is a medium-severity Special Element Injection (CWE-75) vulnerability in Totolink Ex200 Firmware. Its CVSS base score is 6.5 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Content Injection (T1659); ranked at the 32th 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-29679
Vulnerability Data
TOTOLINK EX200 V4.0.3c.7646_B20201211 was discovered to contain a Denial-of-Service (DoS) vulnerability in the RebootSystem function which can reboot the system without authorization.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
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 (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 sanitization to block special-element 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.
Security testing catches injection vulnerabilities but does not itself implement the sanitization fix.
Logging can record injection attempts for detection but does not prevent the weakness.
Secure development life cycle mandates input validation and sanitization practices that directly prevent special-element injection.
Application security requirements explicitly call for controls against injection flaws including special-element handling.
Secure architecture principles reduce injection surfaces but do not prescribe the actual sanitization logic.
Secure coding standards require rigorous input sanitization, directly eliminating CWE-75.