dbcve.org
Zxcloud IraiApplication · Zte

CVE-2023-41776

HIGH · 7.8 CVSS v3.1 Published 2024-01-03
Fix available
A fix is available. Upgrade to 7.23.32 or later.
See remediation →
80/100
Remediation priority · High
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
There is a local privilege escalation vulnerability of ZTE's ZXCLOUD iRAI.Attackers with regular user privileges can create a fake process, and to escalate local privileges.

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 confidence

A local privilege escalation vulnerability exists in ZTE's ZXCLOUD iRAI product. An attacker with standard user-level access can create a fake process to elevate privileges to administrator or root level on the local system.

MitigationApply vendor-supplied patches from ZTE for ZXCLOUD iRAI. Until a patch is available, monitor process creation activities and restrict user access to the system where feasible.

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
Zxcloud IraiApplication
Affected:< 7.23.32

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

CVSS:3.1/AV:L/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. Determine ZXCLOUD iRAI installed version
    Locate and inspect the ZTE ZXCLOUD iRAI installation directory or use the product's version command. Common locations include /opt/zte/irai or the application's about/info panel. Compare the installed version number against the affected range (versions below 7.23.32).
    Affected if The installed version of ZXCLOUD iRAI is lower than 7.23.32
  2. Verify current user privilege level
    Run whoami or id command to determine if the current account has standard user-level access rather than administrator or root privileges.
    Affected if The account being used has standard user-level permissions on the system
  3. Inspect running processes on the system
    Use task manager, ps aux (Linux), or Process Explorer to list all running processes. Look for any unfamiliar or suspicious processes that could indicate fake process creation attempts.
    Affected if Unusual or unauthorized processes are observed running under elevated privileges
  4. Review system logs for process creation events
    Examine system event logs, security logs, or application logs for entries related to process creation, especially those initiated by standard user accounts that resulted in privilege escalation.
    Affected if Logs contain process creation events from standard users that resulted in administrator or root-level execution

You are affected if ZXCLOUD iRAI version is below 7.23.32 and the system permits standard users to create processes that can elevate to administrator or root privileges.

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 7.23.32 or later
Fixed in 7.23.32
Interim mitigation

Apply vendor-supplied patches from ZTE for ZXCLOUD iRAI. Until a patch is available, monitor process creation activities and restrict user access to the system where feasible.

Recommended fix Moderate confidence

7.23.32 or later

  1. 1. Verify current ZXCLOUD iRAI version by checking the application or running: zxcloud --version or irai --version
  2. 2. Confirm the current version is below 7.23.32
  3. 3. Back up all critical data and configurations before upgrading
  4. 4. Download the ZXCLOUD iRAI version 7.23.32 or later from the official ZTE support portal at support.zte.com.cn
  5. 5. Review the release notes for version 7.23.32 to understand any special upgrade requirements
  6. 6. Stop the ZXCLOUD iRAI service before applying the upgrade
  7. 7. Install version 7.23.32 or newer following the standard upgrade procedure
  8. 8. Verify the upgrade was successful by checking the new version number
Caveat Check ZTE release notes for version 7.23.32 for any configuration or compatibility changes before upgrading

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

Fix this in Zxcloud Irai Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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