CVE-2021-37105
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 · uneditedThere is an improper file upload control vulnerability in FusionCompute 6.5.0, 6.5.1 and 8.0.0. Due to the improper verification of file to be uploaded and does not strictly restrict the file access path, attackers may upload malicious files to the device, resulting in the service abnormal.
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 confidenceThere is an improper file upload control vulnerability in Huawei FusionCompute 6.5.0, 6.5.1, and 8.0.0. The system fails to properly validate uploaded files and does not strictly restrict file access paths, allowing attackers to upload malicious files to arbitrary locations on the device, potentially causing service disruption.
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= 6.5.0= 6.5.1= 8.0.0CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed productDetermine if the system is running Huawei FusionCompute. This may be visible in system documentation, the management interface, or by querying the product name through the management portal or command line tools.Affected if The product is not Huawei FusionCompute, then this CVE does not apply.
-
Check the FusionCompute versionLocate and verify the installed version of Huawei FusionCompute. Compare your installed version to the affected versions 6.5.0, 6.5.1, and 8.0.0.Affected if The installed version exactly matches 6.5.0, 6.5.1, or 8.0.0, the system falls within the affected version range.
-
Verify if file upload functionality existsIdentify whether the FusionCompute web management interface or API includes any file upload capability, such as uploading VM images, templates, logs, or configuration files.Affected if File upload functionality is present and accessible to users, the vulnerability surface exists.
-
Inspect upload validation controlsExamine the file upload mechanism for proper validation. Look for whether the system validates file types, restricts file paths, or sanitizes file names before processing uploaded content.Affected if The upload mechanism lacks strict file type validation, does not restrict access paths, or does not sanitize file names, the system is likely vulnerable to the improper file upload flaw described in this CVE.
A system is affected if it runs Huawei FusionCompute version 6.5.0, 6.5.1, or 8.0.0 and has accessible file upload functionality lacking proper validation and path restrictions.
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.
From vendor dataImplement strict file type validation with allowlist approach, sanitize file names to prevent path traversal, restrict upload directories outside web root, and enforce proper access controls on uploaded files.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37105 — 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-2021-37105 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