CVE-2022-23141
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 · uneditedZXMP M721 has an information leak vulnerability. Since the serial port authentication on the ZBOOT interface is not effective although it is enabled, an attacker could use this vulnerability to log in to the device to obtain sensitive information.
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 confidenceZXMP M721 network device contains an authentication bypass in the ZBOOT interface where serial port authentication fails to enforce access controls even when enabled, allowing unauthenticated attackers to gain sensitive information through the serial interface.
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= commond21bootv100004_ls1045CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 device modelAccess the device console or management interface and retrieve the hardware model information. Look for 'ZXMP M721' or 'ZTE M721' in the device inventory or boot messages.Affected if The device is not a ZTE ZXMP M721 unit, then this CVE does not apply.
-
Retrieve the firmware versionConnect to the device serial console and observe boot messages, or use the management CLI to query the installed firmware version. Look for the exact version string.Affected if The installed firmware version is exactly 'commond21bootv100004_ls1045', then this CVE applies. If the version differs, compare to the affected range.
-
Verify ZBOOT interface accessibilityAttempt to access the ZBOOT interface via the serial console. This is typically accessed by interrupting the normal boot process via the serial port.Affected if The ZBOOT interface is reachable without authentication, or accepts commands without login credentials, then the vulnerability is exploitable.
-
Check serial authentication configurationIf you have administrative access, examine the serial port security settings in the device configuration. Look for any 'serial authentication' or 'console authentication' settings.Affected if Serial authentication is enabled but the ZBOOT interface still allows unauthenticated access, then the bypass vulnerability is present.
You are affected if you have a ZTE ZXMP M721 device running firmware version commond21bootv100004_ls1045 and the ZBOOT serial interface is accessible without authentication enforcement.
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.
From vendor dataApply vendor firmware patch if available; if no patch exists, implement network segmentation to restrict physical/logical access to the device's serial interface and monitor for unauthorized access attempts.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23141 — 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-2022-23141 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