dbcve.org
Imx6Application · Ailux

CVE-2023-45597

CRITICAL · 9.0 CVSS v3.1 Published 2024-03-05
Fix available
A fix is available. Upgrade to 1.0.7-2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable

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-1236 “Improper Neutralization of Formula Elements in a CSV File” vulnerability in the “file_configuration” functionality of the web application (concerning the function “export_file”) allows a remote authenticated attacker to inject arbitrary formulas inside generated CSV files. 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

A CSV formula injection vulnerability (CWE-1236) exists in the 'export_file' function of the AiLux imx6 web application's file_configuration module. An authenticated remote attacker can inject malicious spreadsheet formulas (using characters like =, +, -, @) into CSV export fields, which execute when the CSV is opened in spreadsheet software, potentially leading to code execution or data exfiltration.

MitigationUpgrade to AiLux imx6 bundle version imx6_1.0.7-2 or later, which should include proper neutralization of formula characters in CSV exports (e.g., prefixing formula characters with a single quote or applying proper output encoding).

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
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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 installation
    Locate the AiLux imx6 web application in your environment and confirm it is running. Check system inventory or running services for the 'imx6' or 'Ailux' product.
    Affected if The AiLux imx6 web application is present in your environment.
  2. Determine the installed version
    Access the web application's admin panel, system info page, or check version files/configuration to identify the exact bundle version. Compare against the affected range of versions before 1.0.7-2.
    Affected if The installed version is any version earlier than imx6_1.0.7-2.
  3. Verify the file_configuration module is enabled
    Check the web application's module configuration or directory structure for the presence of the 'file_configuration' module. Look for related configuration files or UI options.
    Affected if The file_configuration module is present and enabled in the application.
  4. Confirm CSV export functionality is accessible
    Locate the 'export_file' function within the file_configuration module. This is typically accessible via a web endpoint or administrative interface that allows exporting data to CSV format.
    Affected if The export_file function exists and is accessible to authenticated users.
  5. Assess exposure to authenticated users
    Determine if the application accepts user authentication and if the export_file function is available to standard authenticated users rather than only highly privileged administrators.
    Affected if The application allows authenticated user access to the CSV export feature, enabling formula injection during export.

You are affected if you are running AiLux Imx6 version earlier than 1.0.7-2 with the file_configuration module and its export_file function enabled and accessible to authenticated users.

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 to AiLux imx6 bundle version imx6_1.0.7-2 or later, which should include proper neutralization of formula characters in CSV exports (e.g., prefixing formula characters with a single quote or applying proper output encoding).

Recommended fix Moderate confidence

imx6_1.0.7-2 or later

  1. 1. Identify the current installed version of the AiLux imx6 bundle
  2. 2. Backup all current configurations and data
  3. 3. Upgrade the imx6 bundle to version 1.0.7-2 or later
  4. 4. Verify the upgrade was successful by checking the version number
  5. 5. Test the "file_configuration" export_file functionality to confirm the CSV injection vulnerability is resolved
  6. 6. Monitor for any anomalies in exported CSV files

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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