CVE-2024-12399
Raw vector
CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:P/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N/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:XCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-12399 is a medium-severity Improper Enforcement of Message Integrity During Transmission in a Communication Channel (CWE-924) vulnerability in Schneider Electric (inferred from references). Its CVSS base score is 6.1 (Medium).
Operationally, exploitation aligns with the MITRE ATT&CK technique Security Account Manager (T1003.002); 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 SC-8 (Transmission Confidentiality and Integrity) and SC-16 (Transmission of Security and Privacy Attributes) — 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-12399 is a CWE-924 vulnerability involving improper enforcement of message integrity during transmission in a communication channel. It affects the Human-Machine Interface (HMI), potentially leading to partial loss of confidentiality, loss of integrity, and availability when communications are intercepted. The vulnerability was published on 2025-01-17 with a CVSS v3.1 base score of 7.1 (AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:H/A:H).
An attacker with network access can exploit this vulnerability by performing a man-in-the-middle attack to intercept HMI communications. Exploitation requires high attack complexity and user interaction, but no privileges. Successful attacks can achieve partial loss of confidentiality, high impact on integrity, and high impact on availability of the HMI.
Schneider Electric has published Security and Safety Notice SEVD-2025-014-02, available at https://download.schneider-electric.com/files?p_Doc_Ref=SEVD-2025-014-02&p_enDocType=Security+and+Safety+Notice&p_File_Name=SEVD-2025-014-02.pdf, which provides details on mitigations for this vulnerability.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-50824
Vulnerability Data
CWE-924: Improper Enforcement of Message Integrity During Transmission in a Communication Channel vulnerability exists that could cause partial loss of confidentiality, loss of integrity and availability of the HMI when attacker performs man in the middle attack by intercepting the…
more
communication.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
Requires protection of integrity for transmitted information, directly stopping the failure to verify messages were unmodified in transit.
Associates integrity-related security attributes with exchanged information, helping ensure modification can be detected during transmission.
Protects session authenticity, which structurally reduces the ability to undetectably modify messages in the channel.
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.
Directly requires integrity protection (e.g., signatures/hashes) for data-in-transit, which prevents the described weakness while also addressing confidentiality/availability.
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.
Requires secure information transfer procedures that can include integrity checks.
A.8.20 explicitly requires controls to safeguard the confidentiality and integrity of data passing over networks (item e, plus hardening, filtering, protocol disabling, and virtualized separation), which directly stops exploitation of in-transit message tampering for most transmission scenarios; the bounded remainder is non-network channels or cases where the endpoint itself fails to enforce integrity checks.
A.8.21 requires identifying/implementing network service security features (auth, encryption, connection controls) plus rules for authentication, authorization, monitoring and access means (e.g. VPN); this stops exploitation of in-transit tampering for the subset of cases relying on those network-level protections, but leaves a bounded remainder where message-level integrity (e.g. signatures, MACs) is still absent or insufficient.
A.8.24's rules on algorithm selection, key management, and protecting transmitted information (esp. guidance c) directly stop modification-in-transit by mandating integrity-providing cryptography; remainder is bounded to non-crypto integrity mechanisms (e.g. non-repudiation-only schemes or physical-layer protections)
Application security requirements can specify integrity protection for transmitted messages.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (higher-evidence rows only; rows rated `none` are excluded).
Oracle Linux 8 (4 rules)
- V-248574 YUM must be configured to prevent the installation of patches, service packs, device drivers, or OL 8 system components that have not been digitally signed using a certificate that is recognized and approved by the organization. blocks CWE-924
- V-248823 OL 8 must not have the telnet-server package installed. blocks CWE-924
- V-248827 OL 8 must not have the rsh-server package installed. blocks CWE-924