CVE-2023-33669
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-2023-33669 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 in the top 20% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
Tenda AC8V4.0 running firmware V16.03.34.06 contains a stack-based buffer overflow in the sub_44db3c function that is triggered when processing the timeZone parameter. The flaw is an instance of CWE-787 and received a CVSS 3.1 base score of 9.8, reflecting network attack vector, low attack complexity, and no required authentication or user interaction.
An unauthenticated remote attacker can send a crafted HTTP request containing an oversized timeZone value to the device’s web interface, causing an out-of-bounds write on the stack. Successful exploitation can result in arbitrary code execution, full device compromise, or denial of service.
Public GitHub repositories under DDizzzy79/Tenda-CVE contain technical write-ups and proof-of-concept material for the AC8V4.0/N1 variant, but no vendor advisory or patch information is referenced. The EPSS score is currently 0.3091 with the same peak value recorded.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-37825
Vulnerability Data
Tenda AC8V4.0-V16.03.34.06 was discovered to contain a stack overflow via the timeZone parameter in the sub_44db3c function.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Out-of-bounds writes that corrupt control flow or inject shellcode are rendered non-executable by the same memory protections.
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.
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.
Secure coding directly addresses out-of-bounds writes through language choice and coding standards.
Change management can enforce review gates that catch unsafe memory operations before deployment.