CVE-2016-7110
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 · uneditedHuawei Unified Maintenance Audit (UMA) before V200R001C00SPC200 allows remote attackers to execute arbitrary commands via "special characters," a different vulnerability than CVE-2016-7109.
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 confidenceA command injection vulnerability exists in Huawei Unified Maintenance Audit (UMA) versions prior to V200R001C00SPC200. The flaw allows remote attackers to execute arbitrary operating system commands via specially crafted input containing special characters. This unauthenticated remote code execution vulnerability carries a critical CVSS score of 9.8.
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<= v200r001c00spc100CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 installed Huawei UMA versionAccess the UMA management console or check the system information panel within the product interface to confirm the exact version numberAffected if The installed version is v200r001c00spc100 or any earlier version (anything <= v200r001c00spc100)
-
Verify network exposure of management interfaceDetermine if the UMA web management interface is reachable from untrusted networks or the public internetAffected if The management interface is exposed externally without network segmentation or access controls
-
Review logs for suspicious input patternsExamine authentication and input logs for requests containing special shell characters (such as ; | & $ ` or command substitution syntax) in parameter fieldsAffected if Log entries show unusual character sequences or potential command injection attempts in user input fields
A system is affected if it runs Huawei UMA version v200r001c00spc100 or earlier AND has its management interface accessible to network attackers who could inject specially crafted commands.
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 · scopedUpgrade Huawei UMA to version V200R001C00SPC200 or later. If immediate patching is not feasible, restrict network access to the UMA management interfaces and monitor for suspicious input patterns in logs.
V200R001C00SPC200 or later
- Identify the current version of Huawei Unified Maintenance Audit (UMA) installed in your environment
- Plan maintenance window for the upgrade process
- Download Huawei UMA V200R001C00SPC200 or later from the official Huawei support website
- Follow Huawei's standard upgrade procedure for UMA, typically involving backup of current configuration
- Execute the upgrade to V200R001C00SPC200 or newer version
- Verify the upgrade was successful by checking the new version number
- Validate that the web interface is accessible and the service is running properly
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-2016-7110 — 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-2016-7110 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