CVE-2024-22067
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 · uneditedZTE NH8091 product has an improper permission control vulnerability. Due to improper permission control of the Web module interface, an authenticated attacker may exploit the vulnerability to execute arbitrary commands.
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 confidenceThe ZTE NH8091 contains an improper permission control vulnerability in its Web module interface where authentication is present but authorization checks are insufficient or missing on certain endpoints. This allows an authenticated attacker to bypass intended access restrictions and execute arbitrary operating system commands on the device.
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= znh8091v1.8CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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 the device modelAccess the device's web interface or CLI and retrieve the model information. This is typically visible on the login page, in system status, or via SNMP/CLI commands like 'show system info' or 'device-info'.Affected if The device model is not ZTE NH8091, then it is not affected by this specific CVE.
-
Retrieve the firmware versionIn the web interface, navigate to System > Firmware, System > Status, or a similar diagnostics section to view the installed firmware version. Alternatively, use CLI commands such as 'show version' or 'fwversion'.Affected if The firmware version is exactly znh8091v1.8. Versions other than 1.8 are not affected by this specific CVE.
-
Confirm the web management interface is enabledCheck the device configuration for web interface status. This is typically found in Network > Management > Web, Security > Access Control, or similar sections. Look for settings like 'HTTP/HTTPS Management' or 'Web UI Enable'.Affected if The web management interface is disabled, the attack surface is not present regardless of version.
-
Verify network accessibility of the web interfaceDetermine if the web management port (typically 80 or 443) is exposed to untrusted networks. Check device ACLs, firewall rules, or WAN-side accessibility by attempting to reach the interface IP from an external location or reviewing the network topology and access control lists.Affected if The web interface is only accessible from trusted LAN segments and not from WAN/untrusted networks, the vulnerability cannot be exploited by remote attackers.
The device is affected only if it is a ZTE NH8091 running firmware version znh8091v1.8 AND the web management interface is enabled and accessible to the attacker.
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.
From vendor dataApply vendor-supplied firmware patch when available; restrict network access to the web management interface to trusted IP addresses or disable remote web management until patched.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-22067 — 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-22067 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