CVE-2024-12297
Raw vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2024-12297 is a critical-severity Reliance on Security Through Obscurity (CWE-656) vulnerability in Moxa (inferred from references). Its CVSS base score is 9.2 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique System Information Discovery (T1082); ranked in the top 45% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-8 (Security and Privacy Engineering Principles) and SC-13 (Cryptographic Protection) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-50752
Vulnerability Data
Moxa’s Ethernet switch is vulnerable to an authentication bypass because of flaws in its authorization mechanism. Although both client-side and back-end server verification are involved in the process, attackers can exploit weaknesses in its implementation. These vulnerabilities may enable brute-force…
more
attacks to guess valid credentials or MD5 collision attacks to forge authentication hashes, potentially compromising the security of the device.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.3.4
Mitigating Controls (NIST 800-53 r5) AI
Requires selection and implementation of approved cryptographic methods whose strength does not rest on secrecy of design.
Security and privacy engineering principles explicitly prohibit reliance on obscurity and require documented, verifiable protection mechanisms.
Requires cryptographic or equivalent protection of information at rest, eliminating dependence on obscurity for confidentiality.
Mandates actual cryptographic or equivalent protection of transmitted data rather than depending on hidden algorithms or keys.
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 SDLC practices explicitly reject obscurity-based designs in favor of proven controls.
Risk-management policy can mandate avoidance of obscurity but does not itself implement technical alternatives.
Risk analysis surfaces obscurity as a weakness yet does not prevent its introduction.
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.
Mandates use of cryptography whose strength is independent of secrecy of design or keys.
Requires secure architecture and engineering principles that reject reliance on obscurity.
Requires authentication mechanisms whose strength does not depend on secrecy of implementation.
Secure-coding rules prohibit hidden or undocumented security mechanisms.
Security testing can expose mechanisms whose only protection is obscurity.