cve.bz

CVE-2023-43742 zultys: Improper Authentication

9.8 criticalEPSS 0.9%

Critical (9.8) in zultys. EPSS 0.9% estimated probability of exploitation activity in the next 30 days.

On this page
An authentication bypass 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 unauthenticated attacker to obtain an administrative session via a protection mechanism failure in the authentication function. In normal operation, the Zultys MX Administrator Windows client connects to port 7505 and attempts authentication, submitting the administrator username and password to the server. Upon authentication failure, the server sends a login failure message prompting the client to disconnect. However, if the client ignores the failure message instead and attempts to continue, the server does not forcibly close the connection and processes all subsequent requests from the client as if authentication had been successful.

Severity

CVSS 3.1

9.8 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 61st percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-287 Improper Authentication
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2023-43742 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2023-43742?via=ask-ai-copy and https://cve.bz/cve/CVE-2023-43742?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2023-43742 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
zultys:mx-se_firmwarebefore 16.0.4
zultys:mx-se_firmwarefrom 17.0.6 before 17.0.10
zultys:mx-se_ii_firmwarebefore 16.0.4
zultys:mx-se_ii_firmwarefrom 17.0.6 before 17.0.10
zultys:mx-e_firmwarebefore 16.0.4
zultys:mx-e_firmwarefrom 17.0.6 before 17.0.10
zultys:mx-virtual_firmwarebefore 16.0.4
zultys:mx-virtual_firmwarefrom 17.0.6 before 17.0.10
zultys:mx250_firmwarebefore 16.0.4
zultys:mx250_firmwarefrom 17.0.6 before 17.0.10
zultys:mx30_firmwarebefore 16.0.4
zultys:mx30_firmwarefrom 17.0.6 before 17.0.10

Attack patterns (CAPEC)

  • CAPEC-22 Exploiting Trust in Client Likelihood: High · Severity: High
  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-114 Authentication Abuse Severity: Medium
  • CAPEC-115 Authentication Bypass Severity: Medium
  • CAPEC-151 Identity Spoofing Likelihood: Medium · Severity: Medium
  • CAPEC-194 Fake the Source of Data Severity: Medium
  • CAPEC-593 Session Hijacking Likelihood: High · Severity: Very High
  • CAPEC-633 Token Impersonation Severity: Medium
  • CAPEC-650 Upload a Web Shell to a Web Server Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON