dbcve.org
Imaster Mae MApplication · Huawei

CVE-2021-22299

HIGH · 7.8 CVSS v3.1 Published 2021-02-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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 local privilege escalation vulnerability in some Huawei products. A local, authenticated attacker could craft specific commands to exploit this vulnerability. Successful exploitation may cause the attacker to obtain a higher privilege. Affected product versions include: ManageOne versions 6.5.0,6.5.0.SPC100.B210,6.5.1.1.B010,6.5.1.1.B020,6.5.1.1.B030,6.5.1.1.B040,6.5.1.SPC100.B050,6.5.1.SPC101.B010,6.5.1.SPC101.B040,6.5.1.SPC200,6.5.1.SPC200.B010,6.5.1.SPC200.B030,6.5.1.SPC200.B040,6.5.1.SPC200.B050,6.5.1.SPC200.B060,6.5.1.SPC200.B070,6.5.1RC1.B060,6.5.1RC2.B020,6.5.1RC2.B030,6.5.1RC2.B040,6.5.1RC2.B050,6.5.1RC2.B060,6.5.1RC2.B070,6.5.1RC2.B080,6.5.1RC2.B090,6.5.RC2.B050,8.0.0,8.0.0-LCND81,8.0.0.SPC100,8.0.1,8.0.RC2,8.0.RC3,8.0.RC3.B041,8.0.RC3.SPC100; NFV_FusionSphere versions 6.5.1.SPC23,8.0.0.SPC12; SMC2.0 versions V600R019C00,V600R019C10; iMaster MAE-M versions MAE-TOOL(FusionSphereBasicTemplate_Euler_X86)V100R020C10SPC220.

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

Local privilege escalation vulnerability in Huawei products (ManageOne, NFV_FusionSphere, SMC2.0, iMaster MAE-M) where an authenticated attacker can craft specific commands to gain higher privileges. The vulnerability is locally exploitable and requires prior authentication.

MitigationApply vendor-provided patches or updates to the affected Huawei product versions. Since this is a local privilege escalation, ensure strict access controls and monitor for suspicious command execution.

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
Imaster Mae MApplication
Affected:= v100r020c10spc220
ManageoneApplication
Affected:= 6.5.0= 6.5.1= 6.5.1.1= 8.0.0= 8.0.1
Network Functions Virtualization FusionsphereApplication
Affected:= 6.5.1
Smc2.0 FirmwareOperating system
Affected:= v600r019c00= v600r019c10

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 the installed Huawei product
    Determine which Huawei product is running in your environment (iMaster MAE-M, ManageOne, NFV_FusionSphere, or SMC2.0). Check the system documentation or inventory for the product name.
    Affected if The product is one of iMaster MAE-M, ManageOne, NFV_FusionSphere, or SMC2.0
  2. Check the installed version
    Use the product-specific command or management interface to retrieve the installed version number. Compare it against the affected versions: iMaster MAE-M v100r020c10spc220; ManageOne 6.5.0, 6.5.1, 6.5.1.1, 8.0.0, 8.0.1; NFV_FusionSphere 6.5.1; SMC2.0 v600r019c00, v600r019c10.
    Affected if The installed version matches exactly one of the affected versions listed
  3. Verify authentication access controls
    Review user accounts and authentication methods that have access to the affected product's management interface or command line. Since this vulnerability requires prior authentication, identify which users or groups can log in.
    Affected if Untrusted or low-privilege users have authentication access to the affected product
  4. Audit for privilege escalation indicators
    Review system logs, audit logs, and command history for signs of privilege escalation attempts or unexpected command execution that could indicate exploitation of this vulnerability.
    Affected if Logs show commands executed with elevated privileges by a previously low-privilege authenticated user

You are affected if you are running one of the listed product versions AND untrusted or low-privilege users have authentication access to the system.

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 or updates to the affected Huawei product versions. Since this is a local privilege escalation, ensure strict access controls and monitor for suspicious command execution.

Fix this in Imaster Mae M Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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