UmaApplication · Huawei

CVE-2017-8123

CRITICAL · 9.8 CVSS v3.0 Published 2017-11-22
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
The UMA product with software V200R001 has a privilege elevation vulnerability due to insufficient validation or improper processing of parameters. An attacker could craft specific packets to exploit these vulnerabilities to gain elevated privileges.

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 a privilege elevation vulnerability in Huawei UMA product version V200R001. The vulnerability stems from insufficient validation or improper processing of parameters in the software, allowing attackers to craft specific packets to bypass normal authorization checks and gain elevated privileges. The critical CVSS score of 9.8 indicates this is remotely exploitable without authentication and provides complete system compromise.

MitigationApply the vendor patch from Huawei for V200R001 to address the parameter validation issues. If no patch available, restrict network access to the UMA management interface and implement additional input validation at network perimeter.

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:= v200r001

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 installation
    Identify if Huawei UMA unified management appliance is installed in the environment by reviewing installed software, system inventory, or product documentation
    Affected if Huawei Uma software is present on the system
  2. Check installed version number
    Locate and inspect the version information for the Huawei Uma installation, typically accessible via system about page, command line utility, or configuration file
    Affected if Version displayed is V200R001
  3. Verify management interface exposure
    Determine if the Huawei Uma management interface (typically web-based on ports 80/443 or configured administrative port) is accessible from network segments beyond the trusted administration zone
    Affected if Management interface is reachable from untrusted networks or the internet
  4. Review authentication logs for anomalies
    Examine authentication and access logs for the Uma management interface for signs of unauthorized privilege elevation attempts, unusual API calls, or parameter manipulation patterns
    Affected if Logs show successful or attempted unauthorized privilege escalation activities
  5. Check for unauthorized accounts or privilege changes
    Audit user accounts and privilege assignments within the Uma system for unexpected administrative accounts or roles that were not created through legitimate administrative processes
    Affected if Unexpected accounts with elevated privileges exist in the system

If Huawei Uma version V200R001 is installed and its management interface is network-accessible, the environment is affected by this privilege elevation vulnerability and should be prioritized for patching.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch from Huawei for V200R001 to address the parameter validation issues. If no patch available, restrict network access to the UMA management interface and implement additional input validation at network perimeter.

Fix this in Uma Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,312.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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