CVE-2023-43744
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 · uneditedAn OS command injection vulnerability in Zultys MX-SE, MX-SE II, MX-E, MX-Virtual, MX250, and MX30 with firmware versions prior to 17.0.10 patch 17161 and 16.04 patch 16109 allows an administrator to execute arbitrary OS commands via a file name parameter in a patch application function. The Zultys MX Administrator client has a "Patch Manager" section that allows administrators to apply patches to the device. The user supplied filename for the patch file is passed to a shell script without validation. Including bash command substitution characters in a patch file name results in execution of the provided command.
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 confidenceAn OS command injection vulnerability in Zultys MX voice gateway devices (MX-SE, MX-SE II, MX-E, MX-Virtual, MX250, MX30) allows authenticated administrators to execute arbitrary OS commands through the Patch Manager function. The vulnerability exists because the patch filename parameter is passed to a shell script without input validation, enabling bash command substitution when special characters are included in the filename.
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< 16.0.4>= 17.0.6, < 17.0.10< 16.0.4>= 17.0.6, < 17.0.10< 16.0.4>= 17.0.6, < 17.0.10< 16.0.4>= 17.0.6, < 17.0.10< 16.0.4>= 17.0.6, < 17.0.10< 16.0.4>= 17.0.6, < 17.0.10CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Zultys MX device modelLocate the device model label or check the administrative web interface for the exact model (MX-SE, MX-SE II, MX-E, MX-Virtual, MX250, or MX30)Affected if The device model is one of: MX-SE, MX-SE II, MX-E, MX-Virtual, MX250, or MX30
-
Check the installed firmware versionAccess the administrative web interface and navigate to the system status or version information page to view the current firmware version, or use the CLI command 'show version' if availableAffected if The firmware version is less than 16.0.4, OR greater than or equal to 17.0.6 but less than 17.0.10
-
Verify Patch Manager accessibilityCheck if the Patch Manager function is accessible in the administrative interface. This feature is typically found under the System Administration or Maintenance section of the web UIAffected if An authenticated administrator can access the Patch Manager interface and upload patch files
-
Confirm administrative authentication methodReview how administrator authentication is configured - check if the web administrative interface is exposed and whether strong authentication is enforced for administrative accountsAffected if The administrative web interface is accessible to unauthenticated or weakly authenticated users, or if Patch Manager does not require elevated privilege beyond standard administrator access
The environment is affected if the device is an MX-SE, MX-SE II, MX-E, MX-Virtual, MX250, or MX30 running firmware version less than 16.0.4, or version 17.0.6 through 17.0.9, and the Patch Manager feature is accessible to authenticated administrators.
Generated from the published advisory. Verify against your own configuration.
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 · scoped16.0.417.0.10
Upgrade firmware to version 17.0.10 patch 17161 or 16.04 patch 16109 or later to remediate this vulnerability. Limit administrative access to trusted personnel only until patching is complete.
16.0.4 (patch 16109) for 16.x branch; 17.0.10 (patch 17161) for 17.x branch
- Identify the current firmware version of the Zultys MX device (SE, SE II, E, Virtual, MX250, or MX30)
- If running firmware 16.x branch: Upgrade to version 16.0.4 with patch 16109 or later
- If running firmware 17.x branch: Upgrade to version 17.0.10 with patch 17161 or later
- Access the MX Administrator client and navigate to the Patch Manager section
- Apply the appropriate patch file to remediate the vulnerability
- Verify the firmware version after upgrade confirms the patch level
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43744 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-43744 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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