dbcve.org
Imx6Application · Ailux

CVE-2023-45593

MEDIUM · 6.8 CVSS v3.1 Published 2024-03-05
Fix available
A fix is available. Upgrade to 1.0.7-2 or later.
See remediation →
73/100
Remediation priority · Elevated
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A CWE-184 “Incomplete List of Disallowed Inputs” vulnerability in the embedded Chromium browser (concerning the handling of alternative URLs, other than “ http://localhost” ) allows a physical attacker to read arbitrary files on the file system, alter the configuration of the embedded browser, and have other unspecified impacts to the confidentiality, integrity, and availability of the device. This issue affects: AiLux imx6 bundle below version imx6_1.0.7-2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a CWE-184 vulnerability in the embedded Chromium browser of the AiLux imx6 bundle where the URL allowlist is incomplete. The browser only properly restricts to 'http://localhost' but fails to block alternative URL schemes, allowing a physical attacker to access arbitrary files via file:// URLs and modify browser configuration, impacting confidentiality, integrity, and availability.

MitigationUpgrade to imx6_1.0.7-2 or later which contains the complete URL restriction fix. If upgrade is not immediately possible, implement additional input validation to enforce strict allowlisting of only 'http://localhost' URLs in the embedded browser.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Imx6Application
Affected:< 1.0.7-2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Physical
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the AiLux Imx6 bundle version
    Locate the system information or about page for the AiLux imx6 bundle. Check the version string in the system settings, firmware metadata, or bundle manifest file.
    Affected if The version is lower than 1.0.7-2 (e.g., 1.0.6, 1.0.5, etc.)
  2. Confirm the embedded browser is in use
    Identify whether the application uses the bundled Chromium-based browser component. Check the browser executable path or configuration for references to the embedded browser module.
    Affected if The system uses the embedded Chromium browser from the AiLux imx6 bundle
  3. Inspect the URL allowlist configuration
    Locate and examine the browser or application configuration files that define allowed URL schemes. Look for settings named 'allowlist', 'urlallowlist', 'whitelist', or similar. Check both the application config and browser profile settings.
    Affected if The allowlist permits file:// URLs, contains no explicit block of alternative schemes, or only lists 'http://localhost' without denying other schemes
  4. Test URL scheme restriction
    If you can access the embedded browser interface, attempt to navigate to a file:// URL (e.g., file:///etc/passwd or file://C:\Windows\system32\config\sam) to verify whether the browser blocks or allows it.
    Affected if The browser allows navigation to file:// URLs or displays file contents without blocking the request
  5. Check browser security policy settings
    Examine any security policy, sandbox configuration, or command-line flags passed to the embedded Chromium browser. Look for flags like '--disable-file-access', '--restrict-file-access', or similar restrictions.
    Affected if No file:// scheme restriction flags are present, or the policy explicitly allows file access

If the AiLux Imx6 version is below 1.0.7-2 and the embedded browser configuration allows file:// or non-http://localhost URLs, the environment is affected by this incomplete allowlist vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 1.0.7-2 or later
Fixed in 1.0.7-2
Interim mitigation

Upgrade to imx6_1.0.7-2 or later which contains the complete URL restriction fix. If upgrade is not immediately possible, implement additional input validation to enforce strict allowlisting of only 'http://localhost' URLs in the embedded browser.

Fix this in Imx6 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45593 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-45593 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data