dbcve.org
FusioncomputeApplication · Huawei

CVE-2017-8158

MEDIUM · 6.5 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 →
67/100
Remediation priority · Elevated
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
FusionCompute V100R005C00 and V100R005C10 have an improper authorization vulnerability due to improper permission settings for a certain file on the host machine. An authenticated attacker could create a large number of virtual machine (VM) processes to exhaust system resources. Successful exploit could make new VMs unavailable.

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

FusionCompute V100R005C00 and V100R005C10 contain an improper authorization vulnerability where improper permission settings on a host file allow authenticated users to create an unlimited number of VM processes, leading to resource exhaustion and denial of service for new VM provisioning.

MitigationCorrect the file permissions on the affected host to restrict unauthorized VM process creation, and implement VM creation quotas or rate limiting for authenticated users to prevent resource exhaustion.

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
FusioncomputeApplication
Affected:= v100r005c00= v100r005c10

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/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. Identify FusionCompute version
    Check the installed FusionCompute version via the management console or system information command (e.g., 'fusioncompute -v' or via the admin portal under System > About)
    Affected if Version is exactly V100R005C00 or V100R005C10
  2. Locate host VM process control file
    On the FusionCompute host, identify the configuration file or script that controls VM process creation limits. Check common locations such as /opt/fusioncompute/config/, /usr/local/fusioncompute/, or similar paths for files named with keywords like 'vm', 'quota', 'limit', or 'process'
    Affected if A file controlling VM process creation exists with world-writable or group-writable permissions (e.g., chmod 666 or similar overly permissive settings)
  3. Verify file permissions on VM control file
    Run 'ls -la' on the identified VM process control file and examine the permission bits. Look for permission sets that allow write access to non-privileged users (such as 'other' or group permissions that include authenticated users)
    Affected if Permissions allow authenticated non-admin users to modify VM creation parameters (e.g., permissions like 666, 776, or owner-only but accessible via group)
  4. Check for VM creation quota configuration
    Inspect the FusionCompute quota or rate limiting configuration via the admin console (Navigate to Policy > Quota or similar) or by querying the system for user VM creation limits
    Affected if No per-user or global VM creation quotas are configured, or quotas are set to unlimited/unrestricted for authenticated users
  5. Test VM creation behavior
    As an authenticated non-administrative user, attempt to create multiple VMs in rapid succession beyond reasonable operational limits to observe if the system allows unlimited creation
    Affected if The system allows creation of VMs beyond practical resource limits without enforcing quotas or rate limiting

A user is affected if they are running FusionCompute V100R005C00 or V100R005C10 with improperly permissive file permissions on the VM process control file and no VM creation quotas configured for authenticated users.

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

Correct the file permissions on the affected host to restrict unauthorized VM process creation, and implement VM creation quotas or rate limiting for authenticated users to prevent resource exhaustion.

Fix this in Fusioncompute Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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