CVE-2021-37061
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 · uneditedThere is a Uncontrolled Resource Consumption vulnerability in Huawei Smartphone.Successful exploitation of this vulnerability may lead to Screen projection application denial of service.
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 · low confidenceUncontrolled resource consumption vulnerability in Huawei Smartphone's Screen projection application that can lead to denial of service. The vulnerability has a CVSS score of 7.5 (HIGH), indicating significant impact potential.
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.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.
-
Verify Screen projection feature is enabledCheck the device settings for Screen projection / Smart Projection / Wireless projection functionality. On Huawei devices, this is typically found under Settings > Device Connectivity > Screen projection or Settings > Network & Internet > Screen projection.Affected if Screen projection is actively enabled and in use on a HarmonyOS device below version 2.0
-
Check installed HarmonyOS versionNavigate to Settings > About Phone > Version on the Huawei device, or use the command 'adb shell getprop ro.build.version.harmonyos' if ADB debugging is available.Affected if The displayed HarmonyOS version number is less than 2.0 (e.g., 1.x.x versions)
-
Confirm Screen projection app versionOpen Settings > Apps > Screen projection (or Screen Projection Assistant) and view the app version information under App info.Affected if The Screen projection application version corresponds to a HarmonyOS build below 2.0 and the feature is enabled
The device is affected if Screen projection is enabled and the HarmonyOS version is below 2.0, as the uncontrolled resource consumption vulnerability can be triggered through the projection feature.
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.
dbcve · scoped2.0
Apply available Huawei security patches for the Screen projection application; if no patch exists, contact Huawei product security for remediation guidance.
HarmonyOS 2.0
- Identify the current HarmonyOS version installed on the affected device
- Navigate to Settings > System & Updates > Software Update on the Huawei smartphone
- Check for and install any available HarmonyOS updates
- Verify the device has updated to HarmonyOS version 2.0 or later to confirm the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37061 — 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-37061 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