dbcve.org
Imx6Application · Ailux

CVE-2023-45591

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-122 “Heap-based Buffer Overflow” vulnerability in the “logger_generic” function of the “Ax_rtu” binary allows a remote authenticated attacker to trigger a memory corruption in the context of the binary. This may result in a Denial-of-Service (DoS) condition, possibly in the execution of arbitrary code with the same privileges of the process (root), or have other unspecified impacts on 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

A heap-based buffer overflow (CWE-122) exists in the logger_generic function of the Ax_rtu binary in the AiLux imx6 bundle. A remote authenticated attacker can trigger memory corruption, potentially achieving arbitrary code execution with root privileges or causing denial of service.

MitigationUpdate the AiLux imx6 bundle to version imx6_1.0.7-2 or later to obtain the patched Ax_rtu binary.

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. Locate the Ax_rtu binary
    Search for the Ax_rtu binary on the system using 'find / -name Ax_rtu 2>/dev/null' or check common paths like /usr/bin/, /usr/sbin/, /opt/ailux/bin/
    Affected if The Ax_rtu binary is not found - the product may not be installed or uses a different binary name
  2. Determine the AiLux imx6 bundle version
    Check the installed package version using the system package manager (dpkg -l | grep ailux, rpm -qa | grep imx6, or cat /etc/ailux版本) or check the firmware version file if this is an embedded device
    Affected if The installed version is below 1.0.7-2, or the version cannot be determined and the product is AiLux imx6
  3. Identify the Ax_rtu binary version
    Run 'Ax_rtu --version' or 'Ax_rtu -v' if supported, or use 'file Ax_rtu' and check any embedded version strings with 'strings Ax_rtu | grep -i version'
    Affected if The binary version or build date indicates it is older than the imx6_1.0.7-2 patch release
  4. Check if logger_generic feature is accessible
    Review the Ax_rtu configuration file (typically in /etc/ax_rtu.conf, /etc/ailux/logger.conf, or similar) for the logger_generic module, and verify if remote access/authentication is enabled
    Affected if The logger_generic function is enabled and the service exposes remote network access (not bound to localhost only)
  5. Verify network exposure of Ax_rtu service
    Run 'netstat -tlnp | grep -i ax_rtu' or 'ss -tlnp | grep -i ax_rtu' to determine if Ax_rtu listens on non-localhost interfaces, and review firewall rules
    Affected if Ax_rtu listens on a reachable network interface (0.0.0.0 or external IP) rather than only 127.0.0.1

The environment is affected if the AiLux imx6 bundle version is below 1.0.7-2 OR the Ax_rtu binary predates the patch, and the logger_generic feature is accessible either locally or over the network.

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

Update the AiLux imx6 bundle to version imx6_1.0.7-2 or later to obtain the patched Ax_rtu binary.

Recommended fix High confidence

imx6_1.0.7-2

  1. Upgrade the AiLux imx6 bundle to version imx6_1.0.7-2 or later to remediate the heap-based buffer overflow vulnerability in the Ax_rtu binary's logger_generic function

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
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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