Security Resilience

CVE-2024-12297

Published
15 January 2025
Modified
15 April 2026
CVSS Score v4 9.2
Click a component to see what it means
Raw vectorCVSS: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:X
EPSS Score 0.0085 57th percentile
Risk Priority 47 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

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, ranked in the top 43% 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

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

CVEs Like This One

CVE-2024-9138Shared CWE-656
CVE-2024-5244Shared CWE-656
CVE-2026-7161Shared CWE-656
CVE-2025-59093Shared CWE-656
CVE-2025-7020Shared CWE-656
CVE-2026-42363Shared CWE-656
CVE-2025-25983Shared CWE-656

Affected Assets

Moxa
—
inferred from references and description; NVD did not file a CPE for this CVE

Mitigating Controls

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 (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.

blocks

Mandates use of cryptography whose strength is independent of secrecy of design or keys.

blocks

A.8.27 mandates security-by-design principles (defense-in-depth, least privilege, assume-breach, distrust-external-input, fail-securely, zero-trust verification) plus explicit design reviews against known attack patterns; these stop most obscurity-dependent mechanisms from being chosen or deployed, but a bounded remainder (e.g. vendor-proprietary algorithms or data-hiding choices outside the reviewed architecture layers) can still reach production and be exploitable.

prevents

Secure-coding rules prohibit hidden or undocumented security mechanisms.

blocks

A.8.5 mandates strong, multi-factor, non-obscure authentication techniques and log-on protections; it does not rely on or preserve any obscurity-based mechanism, so it performs no prevention against exploitation of a security-through-obscurity weakness

finds

Security testing can expose mechanisms whose only protection is obscurity.

Hardening callouts derived

DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.

  • No fine-grained STIG row for CWE-656, a class-level weakness, and none of its children carries one either.

References