Cyber Resilience

CVE-2023-45596

Ailux Imx6 ≤ 1.0.7-2

Published
05 March 2024
Modified
23 April 2025
CVSS Score v3.1 5.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0049 40th percentile
Risk Priority 44 floored blend · peak EPSS

Summary

CVE-2023-45596 is a medium-severity Forced Browsing (CWE-425) vulnerability in Ailux Imx6. Its CVSS base score is 5.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 40th 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 AC-24 (Access Control Decisions) and AC-3 (Access Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

A CWE-425 “Direct Request ('Forced Browsing')” vulnerability in the “file_configuration” functionality of the web application allows a remote unauthenticated attacker to access confidential configuration files. This issue affects: AiLux imx6 bundle below version imx6_1.0.7-2.

CWE(s)
CWE-425

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1083 File and Directory Discovery Discovery
Adversaries may enumerate files and directories or may search in specific locations of a host or network share for certain information within a file system.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

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

Affected Assets

ailux
imx6
≤ 1.0.7-2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match

AC-3 directly requires enforcement of authorizations for access to resources such as URLs, scripts, and files, structurally preventing forced browsing.

AC-24 Access Control Decisions good match

AC-24 requires that access-control decisions be applied to every request, addressing the missing enforcement on restricted URLs.

AC-6 Least Privilege partial match

AC-6 requires restricting authorizations to the minimum needed, reducing the set of resources that must be protected against direct requests.

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.

PR.AA-05 full match
prevents

Directly requires policy-driven definition, enforcement, and review of authorizations on resources such as URLs.

PR.IR-01 mostly match
prevents

Protects environments from unauthorized logical access, which includes preventing direct requests to restricted paths.

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing can detect forced-browsing flaws, but the control itself does not prevent them in production.

A.8.3 Information access restriction mostly match
prevents

Information access restriction implements the technical enforcement that directly blocks unauthorized direct requests.

A.5.15 Access control partial match
prevents

Access control policy directly requires authorization checks on all resources, preventing forced browsing.

A.5.18 Access rights partial match
degrades

Managing access rights ensures every URL/script/file is explicitly authorized, mitigating direct request attacks.

A.8.2 Privileged access rights partial match
degrades

Privileged access rights control enforces least-privilege checks on restricted endpoints.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC can include authorization design, yet the control itself does not guarantee runtime enforcement.

References