Security Resilience

CVE-2023-5457

Ailux Imx6 ≤ 1.0.7-2

Published
05 March 2024
Modified
09 April 2025
CVSS Score v3.1 7.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score 0.0064 50th percentile
Risk Priority 58 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-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, ranked at the 50th 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

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

CVEs Like This One

CVE-2023-45595Same product: Ailux Imx6
CVE-2023-5456Same product: Ailux Imx6
CVE-2023-45599Same product: Ailux Imx6
CVE-2023-45600Same product: Ailux Imx6
CVE-2023-45596Same product: Ailux Imx6
CVE-2023-45591Same product: Ailux Imx6
CVE-2023-45597Same product: Ailux Imx6
CVE-2023-45592Same product: Ailux Imx6
CVE-2023-45593Same product: Ailux Imx6
CVE-2023-45594Same product: Ailux Imx6

Affected Assets

ailux
imx6
≤ 1.0.7-2

Mitigating Controls

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.

References