CVE-2021-22484
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 · uneditedSome Huawei wearables have a vulnerability of not verifying the actual data size when reading data. Successful exploitation of this vulnerability may cause a server out of memory (OOM).
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 confidenceThis vulnerability in Huawei wearables stems from the device or companion software failing to validate the actual size of data before reading it into memory buffers. When oversized or malformed data is processed, it can exhaust server-side memory resources, causing an out-of-memory condition. The lack of bounds checking represents a classic resource exhaustion and potential buffer overflow vulnerability in the data handling logic.
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= 2.0.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify HarmonyOS wearable devices in your environmentLocate all Huawei wearable devices (smartwatches, fitness trackers) connected to your network or managed devices. Check device inventories or network scans for Huawei wearable product names.Affected if Any Huawei wearable device is present in the environment
-
Verify HarmonyOS version on the wearable deviceAccess the device settings menu, typically under Settings > About Phone/About Device > Version, or use the companion smartphone app (Huawei Health) to check the installed HarmonyOS version.Affected if The device reports HarmonyOS version exactly 2.0.0
-
Confirm companion software is in useCheck if Huawei Health app or other Huawei companion software is installed on paired smartphones that manage the wearable device.Affected if Companion software is actively used to sync or manage the wearable device
-
Check if data sync features are enabledReview the wearable and companion app settings to confirm data synchronization features (such as health data sync, firmware updates, or notification handling) are enabled.Affected if Data sync or communication features between device and companion software are active
You are affected if you have any Huawei wearable device running exactly HarmonyOS 2.0.0 with active companion software and data sync capabilities enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict data size validation and bounds checking on both client and server sides before any read or memory allocation operations. Limit maximum acceptable data lengths and implement proper error handling for oversized data.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-22484 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-22484 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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