CVE-2024-22062
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 permissions and access control vulnerability in ZXCLOUD IRAI.An attacker can elevate non-administrator permissions to administrator permissions by modifying the configuration.
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 confidenceZXCLOUD IRAI contains a privilege escalation vulnerability where non-administrator users can modify configuration settings to elevate their permissions to administrator level. The application fails to properly validate authorization when configuration parameters are altered, allowing authenticated users with limited privileges to gain full administrative access.
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.40CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/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.
-
Confirm Zte Zxcloud Irai is installedIdentify the installed product name and version through system inventory, application listing, or product-specific commandAffected if The product is Zte Zxcloud Irai and the version is below 7.23.40
-
Verify the installed version numberLocate the application version through product interface, configuration file, or version lookup commandAffected if The installed version is lower than 7.23.40 (e.g., 7.23.30, 7.22.x, etc.)
-
Check for non-administrator user accountsQuery the user management module or user database to list accounts with roles other than administratorAffected if There are authenticated users with limited or non-administrator roles in the system
-
Test configuration modification access for non-admin usersAttempt to access or modify configuration settings using a non-administrator account, particularly settings related to user permissions or rolesAffected if Non-administrator users can alter configuration parameters that affect user roles or permission levels
The environment is affected if Zte Zxcloud Irai version is below 7.23.40 and non-administrator users have the ability to modify configuration settings that can elevate their permissions.
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.40
Restrict configuration modification permissions to administrator-level users only and implement server-side validation to verify the caller's authorization level before permitting any configuration changes that affect user permissions or roles.
7.23.40 or later
- Upgrade Zxcloud Irai to version 7.23.40 or later to remediate the privilege escalation vulnerability
- After upgrading, verify that non-administrator accounts can no longer modify configuration to gain administrator privileges
- Confirm the upgrade was successful by checking the product version in the administration interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2024-22062 — 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-2024-22062 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