CVE-2024-39754
Wavlink Wl-Wn533A8 Firmware m33a8.v5030.210505
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HSummary
CVE-2024-39754 is a critical-severity Hidden Functionality (CWE-912) vulnerability in Wavlink Wl-Wn533A8 Firmware. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Redundant Access (T1108); ranked in the top 32% 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 CM-2 (Baseline Configuration) and CM-7 (Least Functionality) — 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-39754 is a static login vulnerability in the wctrls functionality of the Wavlink AC3000 router running firmware version M33A8.V5030.210505. The issue allows a specially crafted set of network packets to lead to root access on the affected device. It is classified under CWE-912 and was published on 2025-01-14 with a CVSS v3.1 base score of 10.0 (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H), marking it as critical.
An unauthenticated attacker with network access can exploit this vulnerability by sending specially crafted packets to the device. Successful exploitation grants root-level privileges, enabling high-impact compromise of confidentiality, integrity, and availability without requiring privileges, user interaction, or high complexity.
Further technical details are provided in the Talos Intelligence vulnerability report at https://talosintelligence.com/vulnerability_reports/TALOS-2024-2034.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-38370
Vulnerability Data
A static login vulnerability exists in the wctrls functionality of Wavlink AC3000 M33A8.V5030.210505. A specially crafted set of network packets can lead to root access. An attacker can send packets to trigger this vulnerability.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Maintaining and reviewing a documented baseline configuration allows comparison that reveals any functionality absent from the approved specification.
Least-functionality configuration explicitly prohibits or restricts any capability not required by the approved baseline, blocking hidden additions.
Developer testing and evaluation activities are designed to discover undocumented or unspecified functionality after it has been introduced.
Documented development processes and standards require all functionality to be specified and visible, structurally preventing undocumented hidden features.
An SDLC that incorporates security engineering principles mandates that all product functions be part of the approved specification.
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.
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 discover undocumented functionality before release.
Change management processes can catch unauthorized additions but do not inherently prevent hidden functionality from being introduced.
Monitoring activities can detect anomalous behavior from hidden functions but do not eliminate the weakness.
Secure development life cycle mandates documented requirements and design reviews that would expose undocumented hidden functionality.
Application security requirements explicitly define expected functionality, making hidden features a violation.
Secure system architecture and engineering principles require transparent, documented designs that preclude hidden functionality.