HarmonyosOperating system · Huawei

CVE-2021-39988

HIGH · 7.5 CVSS v3.1 Published 2022-01-03
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
The HwNearbyMain module has a NULL Pointer Dereference vulnerability.Successful exploitation of this vulnerability may cause a process to restart.

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 NULL Pointer Dereference vulnerability exists in the HwNearbyMain module, which is part of Huawei's Nearby service functionality. When an attacker triggers the vulnerability by providing specific input that causes a null pointer to be dereferenced, the affected process crashes and restarts, resulting in denial of service.

MitigationApply the vendor patch for CVE-2021-39988 when available, which should include proper null pointer validation in the HwNearbyMain module before dereferencing pointers.

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

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. Check HarmonyOS version
    Navigate to Settings > About Phone > Version on the Huawei device, or run 'getprop ro.build.version.harmonyos' via ADB shell
    Affected if The reported version number is less than 2.0 (e.g., 1.x, 1.5.x, etc.)
  2. Verify HwNearbyMain module presence
    Check for the presence of the HwNearbyMain component in the system. On HarmonyOS devices, this may be found in /system/lib/ or /system/app/ directories, or check via 'pm list packages' for nearby-related packages
    Affected if The HwNearbyMain module or nearby-related package is installed on the device
  3. Confirm Nearby service is enabled
    Go to Settings > Huawei > Nearby (or Settings > Connections > Nearby) on the device and check if the Nearby service toggle is enabled, or check via device management APIs
    Affected if The Nearby service functionality is currently turned on or was recently used
  4. Check for recent crashes
    Review system logs (logcat) or crash reports for patterns of null pointer dereference errors related to the HwNearbyMain process, or check Settings > Huawei > Troubleshooting > Crash logs
    Affected if There are recurring crash logs or restart events tied to the HwNearbyMain or nearby service process

The device is affected if it runs HarmonyOS version below 2.0 and has the HwNearbyMain module present with the Nearby service enabled or recently active.

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 the vendor patch for CVE-2021-39988 when available, which should include proper null pointer validation in the HwNearbyMain module before dereferencing pointers.

Recommended fix Moderate confidence

HarmonyOS 2.0 or later

  1. 1. Identify all devices or systems running HarmonyOS versions prior to 2.0
  2. 2. Check the HarmonyOS update catalog or release notes for version 2.0 availability for your specific device model
  3. 3. Initiate the system update process to upgrade to HarmonyOS 2.0 or later
  4. 4. Verify the update was successful by checking the system version in Settings > About Device
  5. 5. Test the HwNearbyMain module functionality to ensure proper operation after upgrade
Caveat Review release notes for your specific device model for any compatibility changes or feature modifications between your current version and 2.0

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

Fix this in Harmonyos Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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