CVE-2025-62773
Raw vector
CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:NSummary
CVE-2025-62773 is a low-severity Hidden Functionality (CWE-912) vulnerability in Nullvoid (inferred from references). Its CVSS base score is 2.4 (Low).
Operationally, exploitation aligns with the MITRE ATT&CK technique SSH (T1021.004); ranked at the 6th 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 AC-17 (Remote Access) and CM-7 (Least Functionality) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-35314
Vulnerability Data
Mercku M6a devices through 2.1.0 allow TELNET sessions via a router.telnet.enabled.update request by an administrator.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
The vulnerability explicitly enables TELNET access on the device via an administrative request, directly mapping to Remote Services (SSH) technique T1021.004 which covers remote access protocols including TELNET.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly prohibits enabling unnecessary and insecure services such as Telnet on the device.
Restricts remote access methods and explicitly disallows insecure clear-text protocols like Telnet.
Requires confidentiality and integrity protections for transmitted data, which Telnet inherently lacks.
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.