dbcve.org
UmaApplication · Huawei

CVE-2016-7109

CRITICAL · 9.8 CVSS v3.0 Published 2016-09-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Huawei Unified Maintenance Audit (UMA) before V200R001C00SPC200 allows remote attackers to execute arbitrary commands via "special characters," a different vulnerability than CVE-2016-7110.

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

Huawei Unified Maintenance Audit (UMA) versions prior to V200R001C00SPC200 contain a command injection vulnerability where improper handling of special characters in user input allows unauthenticated remote attackers to execute arbitrary operating system commands on the affected device.

MitigationUpgrade Huawei UMA to version V200R001C00SPC200 or later. If immediate patching is not possible, restrict network access to the management interface and implement input validation at upstream network devices.

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
UmaApplication
Affected:<= v200r001c00spc100

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Huawei UMA is present
    Identify if Huawei Unified Maintenance Audit software is installed on the system. This is typically a network management appliance or software running on Huawei hardware.
    Affected if Huawei UMA software is installed on the system
  2. Determine installed version
    Check the installed version of Huawei UMA. This is usually available through the product's web management interface, command-line interface, or system information page. Look for a version string in the format V200R001C00SPCxxx.
    Affected if The installed version is v200r001c00spc100 or earlier (any version prior to V200R001C00SPC200)
  3. Verify management interface accessibility
    Determine if the Huawei UMA web management interface is accessible from the network. This is typically ports 80/443 or a custom management port. Check firewall rules and network access controls.
    Affected if The management interface is accessible from untrusted networks (the vulnerability allows unauthenticated command injection)
  4. Identify user input entry points
    Locate any web forms, API endpoints, or input fields within the Huawei UMA interface that accept user-supplied data, particularly those used in administrative functions.
    Affected if User input fields are present and accept special characters without sanitization (the vulnerable code path)

A system is affected if Huawei UMA is installed with version v200r001c00spc100 or earlier AND the management interface is network-accessible, allowing unauthenticated attackers to inject commands through user input fields.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Huawei UMA to version V200R001C00SPC200 or later. If immediate patching is not possible, restrict network access to the management interface and implement input validation at upstream network devices.

Recommended fix High confidence

V200R001C00SPC200 or later

  1. Obtain the fixed version V200R001C00SPC200 or later from Huawei's official support portal
  2. Review Huawei's upgrade documentation for the Unified Maintenance Audit (UMA) product
  3. Back up the current configuration and data before upgrading
  4. Upload the new version to the UMA appliance following Huawei's standard upgrade procedure
  5. Apply the upgrade and restart the service
  6. Verify the system is running the fixed version (V200R001C00SPC200 or later)
  7. Confirm the vulnerability is resolved by testing that special characters in input fields are properly sanitized

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Uma 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 help mitigating

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-2016-7109 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2016-7109 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