dbcve.org
Imx6Application · Ailux

CVE-2023-5456

CRITICAL · 9.8 CVSS v3.1 Published 2024-03-05
Fix available
A fix is available. Upgrade to 1.0.7-2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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-798 “Use of Hard-coded Credentials” vulnerability in the MariaDB database of the web application allows a remote unauthenticated attacker to access the database service and all included data with the same privileges of the web application. 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 hardcoded credentials vulnerability (CWE-798) in the MariaDB database component of the AiLux imx6 web application allows a remote unauthenticated attacker to gain database access with the web application's privileges. The credentials are embedded in the application bundle.

MitigationReplace hardcoded database credentials with a secure credential management approach (e.g., environment variables, secrets manager, or parameterized configuration) and update the MariaDB instance with new secure credentials. Upgrade to imx6_1.0.7-2 or later.

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

CVSS:3.1/AV:N/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 version
    Locate the imx6 application installation and determine its version number. Check application metadata, About screen, or version file. Compare against the affected range: versions prior to 1.0.7-2 are vulnerable.
    Affected if Installed version is imx6 < 1.0.7-2
  2. Locate application bundle or configuration files
    Find the imx6 application files on the system. Search for configuration directories, application bundles, or deployment packages where the web application stores its components.
    Affected if Application bundle or configuration files exist on the system (prerequisite for further checks)
  3. Search for embedded database credentials
    Within the application bundle or configuration files, search for hardcoded strings that resemble database credentials: look for fields like 'password', 'passwd', 'pwd' in connection strings, config files, or embedded scripts. Examine any MariaDB connection configuration for plaintext credentials.
    Affected if Hardcoded MariaDB credentials are found embedded in application files or configuration
  4. Verify MariaDB access with embedded credentials
    If hardcoded credentials are found in step 3, attempt to authenticate to the MariaDB server using those credentials. Verify if the credentials grant access with the web application's privileges.
    Affected if MariaDB accepts the embedded credentials and grants database access
  5. Check credential management implementation
    Examine how the application manages database credentials: look for environment variables, secrets management integration, or externalized configuration. Determine if credentials are statically embedded rather than dynamically retrieved.
    Affected if Credentials are statically embedded with no evidence of secure credential management (environment variables, secrets manager, or parameterized config)

A user is affected if they run AiLux imx6 version below 1.0.7-2 and the application bundle contains hardcoded MariaDB credentials that can be extracted and used for unauthorized database access.

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

Replace hardcoded database credentials with a secure credential management approach (e.g., environment variables, secrets manager, or parameterized configuration) and update the MariaDB instance with new secure credentials. Upgrade to imx6_1.0.7-2 or later.

Recommended fix Moderate confidence

imx6_1.0.7-2

  1. Identify current AiLux imx6 bundle version
  2. Upgrade the AiLux imx6 bundle to version imx6_1.0.7-2 or later
  3. After upgrading, change the MariaDB database credentials that were hardcoded to unique, secure credentials
  4. Verify the upgrade was successful and the application functions correctly

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

Fix this in Imx6 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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