CVE-2023-25648
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 · uneditedThere is a weak folder permission vulnerability in ZTE's ZXCLOUD iRAI product. Due to weak folder permission, an attacker with ordinary user privileges could construct a fake DLL to execute command 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 · high confidenceZTE ZXCLOUD iRAI contains weak folder permissions that allow unprivileged users to write files to sensitive directories. An attacker with ordinary user access can place a malicious DLL in a folder that is subsequently loaded by a higher-privilege process, achieving local privilege escalation.
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< 7.23.21CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify iRAI installation locationLocate the ZTE ZXCLOUD iRAI installation directory. Common paths include C:\Program Files\ZTE\ or C:\Program Files (x86)\ZTE\. Check your system for folders named iRAI, Zxcloud, or ZTE.Affected if iRAI is installed and the version is below 7.23.21
-
Determine installed versionRight-click the iRAI executable (iraix.exe or similar), select Properties, and check the File Version on the Details tab. Alternatively, open the application and look for About or Help menu to find the version number.Affected if The displayed version is less than 7.23.21
-
Identify application directoriesUse Sysinternals Process Explorer to run iRAI, then right-click the process and select Properties. Note all paths under Module and Environment tabs. Common locations include the installation folder, system temp directories, and Windows folders.Affected if iRAI is running and accessible directories exist on the system
-
Check folder permissions on application directoriesRight-click each identified directory in Windows Explorer, select Properties, then go to the Security tab. Click Advanced to view detailed permissions. Check if Users or other non-privileged groups have Write or Create Files permissions.Affected if Any non-administrator user account has Write permission to a directory where DLLs are loaded by iRAI
-
Inspect DLL search order loadingUse Process Monitor from Sysinternals to trace DLL loading when iRAI starts. Filter by Process Name and Operation CreateFile. Look for DLLs loaded from directories with weak permissions.Affected if DLLs are being loaded from directories writable by unprivileged users
You are affected if ZTE ZXCLOUD iRAI version is below 7.23.21 AND any directory from which the application loads DLLs is writable by non-privileged users.
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 · scoped7.23.21
Restrict folder permissions on affected directories to prevent write access by non-privileged users. Identify all directories accessible by the application process and ensure only administrators can write to locations where DLLs are loaded.
Zxcloud iRAI version 7.23.21 or later
- Verify current ZXCLOUD iRAI version by checking the product interface or using 'irai --version' if available
- Backup all critical data and configurations before performing the upgrade
- Obtain the upgrade package from ZTE official support portal at support.zte.com.cn or through your ZTE support representative
- Follow ZTE's official upgrade documentation to upgrade from current version to version 7.23.21 or later
- After upgrade, verify the folder permissions have been hardened - ensure application folders do not have world-writable permissions
- Restart the iRAI services to apply changes
- Verify the upgrade was successful by checking the version and testing normal operations
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-25648 — 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-25648 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