dbcve.org
Imx6Application · Ailux

CVE-2023-45595

HIGH · 8.8 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 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-434 “Unrestricted Upload of File with Dangerous Type” vulnerability in the “file_configuration” functionality of the web application allows a remote authenticated attacker to upload any arbitrary type of file into 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

The AiLux imx6 web application's 'file_configuration' functionality lacks proper file type validation, allowing authenticated remote attackers to upload files of any extension or content type to the device. This unrestricted file upload vulnerability (CWE-434) could enable execution of malicious code if attacker-uploaded files are subsequently accessible via the web server.

MitigationUpgrade to imx6_1.0.7-2 or later; additionally implement strict allowlist-based file type validation and store uploads outside web-accessible directories.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 installation and version
    Locate the AiLux imx6 web application and determine its installed version number. Consult the application documentation, about page, or system inventory for version information.
    Affected if The installed version is lower than 1.0.7-2
  2. Locate the file_configuration functionality
    Access the web application interface and navigate to or locate the 'file_configuration' feature or module. This may be in settings, configuration, or upload sections of the application.
    Affected if The file_configuration functionality is present and accessible in the web interface
  3. Verify authentication requirements for file_configuration
    Examine whether the file_configuration feature requires authentication to access, and determine what authentication mechanism is in place (if any).
    Affected if The feature can be accessed with valid credentials, or if authentication can be bypassed entirely
  4. Check web server upload directory configuration
    Inspect the web server configuration to determine where uploaded files are stored. Verify if upload directories are located within the web server's document root or are accessible via HTTP/HTTPS.
    Affected if Uploaded files are stored in web-accessible directories and can be served to external users
  5. Determine if file type validation is enforced
    Attempt to upload a file with a non-standard extension (such as .php, .exe, or .json) through the file_configuration feature, or review the application's code/behavior to see if file type restrictions are applied.
    Affected if Files with arbitrary extensions or content types can be uploaded without restriction

If the AiLux imx6 version is below 1.0.7-2, the file_configuration feature is accessible, and uploaded files can be served from web-accessible directories, the environment is affected by this unrestricted file upload 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.

dbcve · scoped
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; additionally implement strict allowlist-based file type validation and store uploads outside web-accessible directories.

Recommended fix Moderate confidence

imx6_1.0.7-2 or later

  1. Identify the current installed version of AiLux imx6 bundle
  2. Obtain the fixed version (imx6_1.0.7-2 or later) from the vendor's official distribution channel
  3. Follow the vendor's standard firmware/software update procedure to apply the upgrade
  4. Verify the upgrade was successful and the version is now 1.0.7-2 or higher
  5. Test that the file_configuration functionality now properly validates file types before accepting uploads

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

Fix this in Imx6 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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