CVE-2023-5457
Ailux Imx6 ≤ 1.0.7-2
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NSummary
CVE-2023-5457 is a high-severity Product Released in Non-Release Configuration (CWE-1269) vulnerability in Ailux Imx6. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 48th 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 CM-2 (Baseline Configuration) and CM-6 (Configuration Settings) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-57771
Vulnerability Data
A CWE-1269 “Product Released in Non-Release Configuration” vulnerability in the Django web framework used by the web application (due to the “debug” configuration parameter set to “True”) allows a remote unauthenticated attacker to access critical information and have other unspecified…
more
impacts to the confidentiality, integrity, and availability of the application. This issue affects: AiLux imx6 bundle below version imx6_1.0.7-2.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 6 hardening rules · 5 OS baselines
—
Mitigating Controls (NIST 800-53 r5) AI
Baseline configuration defines the approved production settings and prevents shipment while still in manufacturing or debug mode.
Establishing and enforcing the most restrictive configuration settings ensures the released product uses hardened production values.
Developer configuration management requires tracking and controlling the transition from manufacturing to release configuration.
Developer testing and evaluation can discover that the delivered build remains in a pre-production configuration.
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.
Configuration management with hardened baselines directly prevents shipping pre-production or debug builds.
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.
Configuration management directly prevents release of non-release builds by enforcing approved, documented configurations.
Security testing and acceptance criteria can detect and block deployment of pre-production builds.
Change-management procedures ensure only approved, release-ready configurations are deployed.
Controlling software installation on operational systems reduces the chance that pre-production builds reach production.
Secure development life-cycle practices include release-gate checks that catch non-release configurations.
Separation of development, test and production environments prevents accidental promotion of non-release configurations.
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` (authoritative rows only; rows rated `none` are excluded).
Oracle Linux 8 (1 rule)
- V-248521 OL 8 must be a vendor-supported release. prevents CWE-1269
RHEL 7 (1 rule)
- V-204458 The Red Hat Enterprise Linux operating system must be a vendor supported release. prevents CWE-1269