Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2024-50667 is a critical-severity Classic Buffer Overflow (CWE-120) vulnerability in Trendnet Tew-820Ap 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 7% of CVEs by exploit likelihood; 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-50667 is a stack-based buffer overflow in the boa httpd web server component of the Trendnet TEW-820AP wireless access point running firmware 1.01.B01. The flaw exists in the IPv6 address handling routines exposed at the endpoints /boafrm/formIPv6Addr, /boafrm/formIpv6Setup, and /boafrm/formDnsv6; insufficient validation of supplied IPv6 address values allows an attacker-supplied payload to exceed the allocated stack buffer, triggering CWE-120.
An unauthenticated remote attacker can send a crafted HTTP POST request to any of the affected endpoints and achieve arbitrary code execution or a denial-of-service condition on the device. The vulnerability carries a CVSS 3.1 base score of 9.8, reflecting network attack vector, low complexity, and no required credentials or user interaction.
The vendor’s support page for the TEW-820AP does not list a firmware update that resolves the issue; the public technical report on GitHub provides proof-of-concept details but no official patch guidance.
EPSS for the CVE rose from a low baseline to a peak of 0.1988 (current value 0.1648), indicating measurable post-disclosure exploitation interest that warrants renewed attention from network defenders.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-44993
Vulnerability Data
The boa httpd of Trendnet TEW-820AP 1.01.B01 has a stack overflow vulnerability in /boafrm/formIPv6Addr, /boafrm/formIpv6Setup, /boafrm/formDnsv6. The reason is that the check of ipv6 address is not sufficient, which allows attackers to construct payloads for attacks.
- 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 analysis can find missing size checks before deployment.
Input validation directly enforces size checks before buffer copies.
Engineering principles require bounds checking and safe buffer handling in design.
Memory protection limits the impact of an overflow once it occurs.
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 directly enforce bounds checking and input validation that prevent classic buffer overflows.
Vulnerability identification processes such as code review or scanning detect classic buffer overflows before exploitation.
Routine patching replaces vulnerable code containing unchecked buffer copies with corrected versions.
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 buffer overflows through fuzzing and static analysis, though it does not prevent them at the source.
Secure development life cycle mandates processes that can include input validation and bounds checking to prevent buffer overflows.
Application security requirements can specify input-size validation and safe buffer handling to mitigate classic buffer overflows.
Secure system architecture and engineering principles promote defensive coding patterns that reduce the likelihood of unchecked buffer copies.