Zxcloud IraiApplication · Zte

CVE-2018-7365

HIGH · 7.2 CVSS v3.0 Published 2018-12-20
Fix available
A fix is available. Upgrade to after 5.01.05 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
All versions up to ZXCLOUD iRAI V5.01.05 of the ZTE uSmartView product are impacted by untrusted search path vulnerability, which may allow an unauthorized user to perform unauthorized operations.

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

This is an untrusted search path vulnerability in ZTE uSmartView (versions up to ZXCLOUD iRAI V5.01.05). The application likely loads libraries or executables from a search path that can be influenced by an unauthorized user, potentially allowing DLL hijacking or binary planting attacks that could lead to unauthorized operations.

MitigationApply vendor-supplied patch or update to ZXCLOUD iRAI V5.01.05 or later; if no patch available, review and restrict file system permissions on directories in the application search path to prevent injection of malicious binaries.

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:<= 5.01.05
UsmartviewApplication
Affected:all versions

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

CVSS:3.0/AV:N/AC:L/PR:H/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. Identify if ZTE uSmartView or ZXCLOUD iRAI is installed
    Search for the application in common installation directories (e.g., C:\Program Files\ZTE, C:\Program Files (x86)\ZTE) or check the Windows registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall for ZTE entries
    Affected if Either product is found on the system
  2. Determine the installed version of ZXCLOUD iRAI
    Locate the application executable (typically named something like irai.exe or similar) and check its file properties to view the version, or run 'wmic product where "name like '%iRAI%'" get version' if available
    Affected if The version number is 5.01.05 or lower
  3. Confirm uSmartView installation regardless of version
    Search for any uSmartView-related executables or check installation folders for uSmartView components; note that all versions are affected per the CVE
    Affected if uSmartView is present at any version
  4. Verify the application is executable or configured to run
    Check if the main application binary (irai.exe or uSmartView.exe) exists and has executable permissions; also check if there are any startup configurations or scheduled tasks
    Affected if The vulnerable application binary is present and has execute permissions
  5. Assess file system permissions on application directories
    Review permissions on the installation directory and subdirectories using 'icacls <directory>' or file explorer security tab - check if non-privileged users have write access to directories in the application search path
    Affected if Users with low privileges can write to directories within the application's base path or search path

The environment is affected if ZXCLOUD iRAI version 5.01.05 or lower is installed, or if uSmartView is present at any version, and the application directory permissions allow unauthorized users to inject malicious binaries into the search path.

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.

From vendor data
Upgrade available Upgrade to a release after 5.01.05
Interim mitigation

Apply vendor-supplied patch or update to ZXCLOUD iRAI V5.01.05 or later; if no patch available, review and restrict file system permissions on directories in the application search path to prevent injection of malicious binaries.

Fix this in Zxcloud Irai Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
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,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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