Zxcloud IraiApplication · Zte

CVE-2023-41779

MEDIUM · 5.5 CVSS v3.1 Published 2024-01-03
Fix available
A fix is available. Upgrade to 7.23.32 or later.
See remediation →
57/100
Remediation priority · Elevated
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 an illegal memory access vulnerability of ZTE's ZXCLOUD iRAI product.When the vulnerability is exploited by an attacker with the common user permission, the physical machine will be crashed.

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

ZTE ZXCLOUD iRAI contains an illegal memory access vulnerability that can be exploited by an attacker with standard user privileges to crash the underlying physical machine, resulting in denial of service.

MitigationApply vendor-provided security patches or updates for ZXCLOUD iRAI; restrict user permissions and implement network segmentation to limit exposure until patch is available.

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify ZXCLOUD iRAI installation
    Locate the ZXCLOUD iRAI installation directory or check the product's web interface for version information. Common locations include the product's admin panel, about page, or version configuration file.
    Affected if The installed version cannot be determined or is confirmed to be below 7.23.32
  2. Verify installed version number
    Retrieve the exact version number of the ZXCLOUD iRAI instance using the product's built-in version check command, configuration file, or management interface.
    Affected if The version is lower than 7.23.32 (for example, 7.23.30, 7.22.x, or earlier releases)
  3. Confirm user authentication is enabled
    Verify that standard user accounts can authenticate to the ZXCLOUD iRAI system. Check user role configurations and confirm that non-privileged accounts have access to the platform.
    Affected if Standard user accounts exist and can log in to the system
  4. Check service accessibility
    Confirm the ZXCLOUD iRAI service is running and network-accessible. Test connectivity to the management interface or API endpoints.
    Affected if The service is exposed on the network and accepts user connections

The environment is affected if ZXCLOUD iRAI is running with a version lower than 7.23.32 and standard user accounts can access the system.

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-provided security patches or updates for ZXCLOUD iRAI; restrict user permissions and implement network segmentation to limit exposure until patch is available.

Recommended fix Moderate confidence

7.23.32

  1. Identify the current version of Zxcloud iRAI installed on the system
  2. Access the ZTE support portal at support.zte.com.cn and locate the download for iRAI version 7.23.32 or later
  3. Obtain the official upgrade package following ZTE's download/approval process
  4. Review any upgrade documentation provided by ZTE for iRAI
  5. Execute the upgrade procedure according to ZTE's documented upgrade process for the iRAI product
  6. After upgrade completion, verify the installed version is 7.23.32 or higher
  7. Confirm the iRAI service is running normally and accessible

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-41779 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