CVE-2024-57703
Memory Safety in Tenda Ac8 Firmware 16.03.34.06
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-57703 is a critical-severity Out-of-bounds Write (CWE-787) vulnerability in Tenda Ac8 Firmware. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 43th percentile by exploit likelihood (below the median); 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 SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2024-57703 is a stack-based buffer overflow vulnerability in Tenda AC8v4 firmware version V16.03.34.06. The issue affects the setSchedWifi function within the /goform/openSchedWifi endpoint, where manipulation of the schedEndTime argument triggers the overflow. This flaw is classified under CWE-787 (Out-of-bounds Write) and CWE-120 (Buffer Copy without Checking Size of Input), earning a CVSS v3.1 base score of 9.8, indicating critical severity due to its network accessibility, low attack complexity, and lack of prerequisites.
An unauthenticated remote attacker can exploit this vulnerability by sending a specially crafted HTTP request to the affected web interface over the network. Successful exploitation leads to a stack-based buffer overflow, potentially allowing arbitrary code execution, denial of service, or unauthorized access with high impacts on confidentiality, integrity, and availability (C:H/I:H/A:H).
Mitigation details and proof-of-concept information are available in the referenced advisory at https://github.com/Pr0b1em/IoT/blob/master/Tenda%20AC8v4%20V16.03.34.06.md. Security practitioners should check for firmware updates from Tenda and apply network segmentation or exposure controls to vulnerable devices until patched.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-53714
Vulnerability Data
Tenda AC8v4 V16.03.34.06 has a stack overflow vulnerability. Affected by this vulnerability is the function setSchedWifi of the file /goform/openSchedWifi. The manipulation of the argument schedEndTime leads to stack-based buffer overflow.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.1
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.
Input validation directly enforces size checks before buffer copies.
Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.
Engineering principles require bounds checking and safe buffer handling in design.
Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.
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-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.
Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.
Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.
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 coding directly requires bounds-checked memory operations, addressing the root cause of CWE-120.
Security testing in development and acceptance can detect and prevent out-of-bounds write defects.
Secure development life cycle mandates practices that prevent out-of-bounds writes.
Application security requirements can specify bounds-checking and safe memory handling.
Secure architecture and engineering principles reduce the likelihood of buffer overflows.
Change management can enforce review gates that catch unsafe memory operations before deployment.