CVE-2024-0323
Br-Automation Automation Runtime ≤ i4.93
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2024-0323 is a critical-severity Use of a Cryptographic Primitive with a Risky Implementation (CWE-1240) vulnerability in Br-Automation Automation Runtime. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked at the 13th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2024-16119
Vulnerability Data
The FTP server used on the B&R Automation Runtime supports unsecure encryption mechanisms, such as SSLv3, TLSv1.0 and TLS1.1. An network-based attacker can exploit the flaws to conduct man-in-the-middle attacks or to decrypt communications between the affected product clients.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 12 hardening rules · 3 OS baselines
—
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requires specific, validated cryptographic primitives, reducing use of risky or improperly implemented primitives.
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 directly require use of approved, proven cryptographic implementations and forbid risky custom ones.
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 approved cryptographic controls, directly preventing use of risky or non-compliant implementations.
Secure SDLC requires vetted crypto libraries and standards, reducing risky custom implementations.
A.8.26 requires that security requirements (including use of cryptography per 8.24) be identified and specified during development or acquisition; it does not itself enforce, implement, or assure a standards-compliant cryptographic primitive and therefore does not stop exploitation of a risky implementation that remains present.
A.8.27 mandates applying security-by-design principles (including least privilege, defense-in-depth, fail securely, distrust external input, and zero-trust verification) plus security-oriented design reviews that can catch and block risky crypto implementations before they ship, but this is only a minority slice of CWE-1240 because the weakness can still arise from non-compliant library selection, post-design changes, or outsourced code where the principles are not rigorously enforced.
Secure coding standards prohibit non-standard or disallowed cryptographic algorithms.
Security testing can detect use of weak or non-compliant cryptographic primitives before deployment.
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 (2 rules)
- V-248524 OL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. blocks CWE-1240
- V-248534 OL 8 must employ FIPS 140-2 approved cryptographic hashing algorithms for all stored passwords. blocks CWE-1240
Oracle Linux 9 (1 rule)
- V-271628 OL 9 must employ FIPS 140-3 approved cryptographic hashing algorithms for all stored passwords. blocks CWE-1240
RHEL 8 (2 rules)
- V-230223 RHEL 8 must implement NIST FIPS-validated cryptography for the following: To provision digital signatures, to generate cryptographic hashes, and to protect data requiring data-at-rest protections in accordance with applicable federal laws, Executive Orders, directives, policies, regulations, and standards. blocks CWE-1240
- V-230224 All RHEL 8 local disk partitions must implement cryptographic mechanisms to prevent unauthorized disclosure or modification of all information that requires at rest protection. blocks CWE-1240