dbcve.org
HarmonyosOperating system · Huawei

CVE-2021-37060

HIGH · 7.5 CVSS v3.1 Published 2021-12-07
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 Improper Input Validation vulnerability in Huawei Smartphone.Successful exploitation of this vulnerability may lead to SAMGR Heap Address Leakage.

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

Improper input validation in Huawei Smartphone's SAMGR (Service Architecture Manager) system service allows attackers to leak heap memory addresses. This information disclosure could potentially aid in developing exploit chains for other vulnerabilities.

MitigationApply vendor-supplied firmware patches from Huawei. Until patched, minimize exposure to untrusted inputs via the SAMGR service.

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Confirm device is running Huawei HarmonyOS
    Check device system information - go to Settings > About Phone > Model/Version information, or run 'getprop ro.build.version.harmonyos' via ADB shell if available
    Affected if The device is not a Huawei device running HarmonyOS (e.g., Android devices, other OS) - this CVE does not apply
  2. Determine installed HarmonyOS version
    Navigate to Settings > About Phone > Version, or use ADB command 'getprop ro.build.version.harmonyos' to retrieve the exact version number
    Affected if Version number is below 2.0 (e.g., 1.0.x, 1.5.x) - the device is affected if version cannot be determined or shows < 2.0
  3. Verify SAMGR service is present
    Check if the SAMGR system service is accessible on the device - attempt to query service list via 'bm dump -a' or check /system/etc/samgr files if available on the device
    Affected if SAMGR service exists and is running on the device - the vulnerability is in this component
  4. Check for heap memory exposure indicators
    Monitor network traffic or IPC communications to SAMGR service for unusual responses that may contain memory addresses, or review any available service logs if debug mode is enabled
    Affected if Service responses contain hex values that appear to be memory addresses being returned to untrusted inputs

A Huawei HarmonyOS device running version below 2.0 with the SAMGR service accessible and returning memory address information in responses indicates the device is affected by this CVE.

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 patches from Huawei. Until patched, minimize exposure to untrusted inputs via the SAMGR service.

Recommended fix High confidence

HarmonyOS 2.0 or later

  1. Back up important data from the device before upgrading
  2. Ensure the device has sufficient battery charge (at least 50%)
  3. Connect the device to a stable Wi-Fi network
  4. Go to Settings > System & Updates > Software Update on the Huawei device
  5. Check for available updates and download HarmonyOS 2.0 or later
  6. Follow the on-screen prompts to install the update
  7. After the update completes, verify the system is running HarmonyOS 2.0 or higher
Caveat Users should note that some legacy applications or custom configurations may not be compatible with HarmonyOS 2.0; ensure critical apps are supported before upgrading

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

Fix this in Harmonyos Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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