dbcve.org
Imx6Application · Ailux

CVE-2023-45594

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-552 “Files or Directories Accessible to External Parties” vulnerability in the embedded Chromium browser allows a physical attacker to arbitrarily download/upload files to/from the file system, with 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 · high confidence

An embedded Chromium browser in the AiLux imx6 bundle below version imx6_1.0.7-2 contains a CWE-552 vulnerability that allows a physically proximate attacker to arbitrarily read from and write files to the device's file system through the browser.

MitigationUpgrade the AiLux imx6 bundle to version imx6_1.0.7-2 or later to incorporate the patched Chromium browser. Additionally, restrict physical access to the device and implement filesystem permissions to limit the impact of any future browser vulnerabilities.

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 AiLux imx6 bundle version
    Check the installed firmware or bundle version by examining system information files, typically found in /etc/version, /opt/ailux/version, or through a systeminfo command if available. Look for a version string containing 'imx6' followed by a version number.
    Affected if The version string shows imx6_1.0.7-2 or any version lower (e.g., imx6_1.0.6, imx6_1.0.5, etc.)
  2. Verify embedded Chromium browser presence
    Locate the embedded Chromium browser binary or package within the device. Common paths may include /usr/bin/chromium, /opt/chromium, or bundled within /usr/local/ailux/. Use 'find' or 'ls' to search for chromium-related executables.
    Affected if An embedded Chromium browser executable exists on the device file system
  3. Confirm browser is accessible to users
    Check file permissions on the Chromium binary and its data directories. Use 'ls -la' on the chromium binary path and verify execute permissions exist for user accounts that could launch the browser.
    Affected if The Chromium browser can be executed by non-privileged users or processes on the system
  4. Check physical access exposure
    Evaluate whether the device has exposed debug ports, USB ports, or network-accessible interfaces that would allow a physically proximate attacker to interact with the embedded browser.
    Affected if Physical access ports or interfaces are available without additional authentication

The environment is affected if it runs an AiLux imx6 bundle version below 1.0.7-2 that includes an accessible embedded Chromium browser, allowing a physically proximate attacker to interact with the file system through the browser.

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.

dbcve · scoped
Upgrade available Upgrade to 1.0.7-2 or later
Fixed in 1.0.7-2
Interim mitigation

Upgrade the AiLux imx6 bundle to version imx6_1.0.7-2 or later to incorporate the patched Chromium browser. Additionally, restrict physical access to the device and implement filesystem permissions to limit the impact of any future browser vulnerabilities.

Recommended fix Moderate confidence

imx6_1.0.7-2 or later

  1. Identify the current installed version of the AiLux imx6 bundle
  2. Obtain the fixed version imx6_1.0.7-2 or later from the official vendor
  3. Follow the vendor's documented upgrade procedure to apply the update to the imx6 device
  4. Verify the upgrade was successful and the embedded Chromium browser is updated to the fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Imx6 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45594 — 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-45594 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