dbcve.org
FusioncomputeApplication · Huawei

CVE-2021-37102

HIGH · 8.8 CVSS v3.1 Published 2021-11-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
There is a command injection vulnerability in CMA service module of FusionCompute product when processing the default certificate file. The software constructs part of a command using external special input from users, but the software does not sufficiently validate the user input. Successful exploit could allow the attacker to inject certain commands to the system. Affected product versions include: FusionCompute 6.0.0, 6.3.0, 6.3.1, 6.5.0, 6.5.1, 8.0.0.

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 · high confidence

A command injection vulnerability exists in the CMA (Cluster Management Agent) service module of Huawei FusionCompute when processing default certificate files. The software incorporates external user input into a command string without proper validation or sanitization, allowing an authenticated attacker to inject arbitrary shell commands. Successful exploitation grants command execution with the privileges of the CMA service.

MitigationApply vendor-provided patches for the affected FusionCompute versions (6.0.0 through 8.0.0). If patches are unavailable, implement strict input validation on certificate file processing within the CMA service and restrict CMA module access to trusted users only.

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:= 6.0.0= 6.3.0= 6.3.1= 6.5.0= 6.5.1= 8.0.0

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

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

  1. Identify FusionCompute version
    Query the FusionCompute management interface or use the 'vradmin' command line tool to retrieve the installed version (e.g., 'vradmin -version' or check the About page in the management console)
    Affected if The installed version matches exactly 6.0.0, 6.3.0, 6.3.1, 6.5.0, 6.5.1, or 8.0.0
  2. Verify CMA service is running
    Check the status of the CMA (Cluster Management Agent) service via the FusionCompute management interface or by querying the service process on the management node (e.g., 'service cma status' or similar admin command)
    Affected if The CMA service is active and processing certificate files
  3. Locate default certificate files
    Inspect the CMA service configuration directory for default certificate files (typically found in /usr/local/cma or similar installation path under a certificates or ssl subdirectory)
    Affected if Default certificate files exist and are being used by the CMA service without custom validation rules
  4. Check CMA access controls
    Review user access permissions for the CMA service module through the FusionCompute RBAC (Role-Based Access Control) configuration to determine if untrusted users can access certificate processing functions
    Affected if Users with limited or untrusted privileges can access or trigger certificate file processing in CMA

You are affected if your FusionCompute version is exactly 6.0.0, 6.3.0, 6.3.1, 6.5.0, 6.5.1, or 8.0.0 AND the CMA service is running with default certificate files accessible to 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

Apply vendor-provided patches for the affected FusionCompute versions (6.0.0 through 8.0.0). If patches are unavailable, implement strict input validation on certificate file processing within the CMA service and restrict CMA module access to trusted users only.

Fix this in Fusioncompute Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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