LiveActive security incident?Get immediate response
CVE Record

CVE-2021-37000: Some Huawei wearables have a permission management vulnerability.

Some Huawei wearables have a permission management vulnerability.

HighCVSS 7.7Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-37000 is a high-severity permission management issue affecting some Huawei wearable devices associated with HarmonyOS 2.0. A local attacker could potentially gain unauthorized access to sensitive information or alter data. The public record is sparse, so exposure assessment should focus on confirmed Huawei wearable inventory and Huawei’s bulletin.

Executive priority

Treat this as a targeted device-management issue, not a broad network emergency. Prioritize environments using Huawei wearables in regulated, executive, operational, or sensitive-data contexts.

Technical view

The CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, scoring 7.7. The issue is categorized under CWE-255 and CWE-276, indicating credential or permission management weakness. Sources do not provide component-level detail, affected model names, exploit primitives, or fixed build identifiers.

Likely exposure

Organizations are most likely exposed if they manage Huawei wearables running HarmonyOS 2.0. The local attack vector reduces internet-scale risk, but no privileges or user interaction are required once local access conditions exist.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. Public details do not include exploit availability, attack procedure, or real-world incident reporting.

Researcher notes

Evidence is incomplete. The public description only states a permission management vulnerability in some Huawei wearables. Do not infer affected models, exploitability beyond the CVSS vector, or remediation specifics without Huawei bulletin confirmation.

Mitigation direction

  • Review Huawei’s wearable security bulletin for CVE-2021-37000 guidance.
  • Update affected HarmonyOS 2.0 wearables according to Huawei’s instructions.
  • Inventory Huawei wearables before assuming exposure is absent.
  • Remove unmanaged affected wearables from sensitive workflows until addressed.
  • Reduce local access to affected devices where practical.

Validation and detection

  • Identify Huawei wearables running HarmonyOS 2.0 in asset records.
  • Compare device firmware or patch level against Huawei’s bulletin.
  • Confirm whether affected devices are managed, updated, or retired.
  • Document compensating controls for devices awaiting vendor remediation.
  • Track CVE status for any later vendor clarification.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-255: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cwe · low confidence lookup

CWE-276: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-37000 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.7 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.7CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N2.55.2Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.7High
CVSS 3.1 vector shape for CVE-2021-37000Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
HuaweiHarmonyOS2.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-255 · source CWE mapping

Credentials Management Errors

Credentials Management Errors represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

CWE-276 · source CWE mapping

Incorrect Default Permissions

Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.