HarmonyosOperating system · Huawei

CVE-2021-40029

HIGH · 7.5 CVSS v3.1 Published 2022-01-10
Fix available
A fix is available. Upgrade to 2.0 or later.
See remediation →
84/100
Remediation priority · High
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
There is a Buffer overflow vulnerability due to a boundary error with the Samba server in the file management module in smartphones. Successful exploitation of this vulnerability may affect function stability.

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

A buffer overflow vulnerability exists in the Samba server component within the file management module of smartphones, caused by a boundary error. This flaw could allow an attacker to potentially execute arbitrary code or destabilize function operation, as reflected by the CVSS 7.5 severity rating.

MitigationApply vendor-supplied firmware updates for affected smartphone models when available; until then, disable the Samba server functionality in the file management module if not required, and restrict network exposure.

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
HarmonyosOperating system
Affected:< 2.0
EmuiOperating system
Affected:= 10.0.0= 10.1.0= 10.1.1= 11.0.0= 11.0.1= 12.0.0
Magic UiOperating system
Affected:= 3.0.0= 3.1.0= 3.1.1= 4.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
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 checks

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

  1. Identify your smartphone OS and version
    Go to Settings > About Phone on your Huawei device and note the OS name (HarmonyOS, EMUI, or Magic UI) and the exact version number displayed
    Affected if The OS is HarmonyOS version less than 2.0, or EMUI versions 10.0.0, 10.1.0, 10.1.1, 11.0.0, 11.0.1, or 12.0.0, or Magic UI versions 3.0.0, 3.1.0, 3.1.1, or 4.0.0
  2. Locate the Samba server feature in file management
    Open the Files app or File Manager on your Huawei smartphone, then look in settings or menu options for Samba server, SMB sharing, or network file sharing settings
    Affected if The Samba server or SMB sharing feature is present and accessible in the file management module, indicating the vulnerable component exists on your device
  3. Verify if Samba server is currently enabled
    In the File Manager settings, check whether the Samba server or network sharing feature is turned on or active
    Affected if The Samba server functionality is enabled or running on your device, making it potentially exploitable if the OS version is in the affected list

Your device is affected if it runs HarmonyOS, EMUI, or Magic UI within the specified version ranges AND has the Samba server feature enabled in the file management module.

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.

dbcve · scoped
Upgrade available Upgrade to 2.0 or later
Fixed in 2.0
Interim mitigation

Apply vendor-supplied firmware updates for affected smartphone models when available; until then, disable the Samba server functionality in the file management module if not required, and restrict network exposure.

Recommended fix Moderate confidence

HarmonyOS 2.0 or later; EMUI 11.0.1 or later; Magic UI 4.1.0 or later (latest available for your specific device model)

  1. Identify the affected device model running HarmonyOS, EMUI, or Magic UI
  2. Check current OS version in Settings > About Phone
  3. Upgrade to HarmonyOS 2.0 or later version (or the latest available version for your device)
  4. If direct upgrade is not available, check for and apply any available system updates from Huawei/Honor
  5. After upgrade, verify the Samba file sharing functionality works correctly
Caveat Upgrading major OS versions may reset some settings; back up data before proceeding; some legacy Samba configurations may need to be re-created after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Harmonyos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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