CVE-2020-9158
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 Missing Cryptographic Step vulnerability in Huawei Smartphone. Successful exploitation of this vulnerability may cause DoS of Samgr.
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 involves a missing cryptographic step in Huawei smartphones that can lead to denial of service of the Samgr system service. The lack of proper cryptographic validation in a security-relevant operation allows an attacker to trigger a DoS condition against this critical system component.
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= 8.0= 8.2= 9.1.0= 9.1.1= 10.0.0= 10.1.0= 10.1.1= 11.0.0= 2.1.1= 3.0.0= 3.1.0= 3.1.1= 4.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 installed EMUI or Magic UI versionOn the smartphone, go to Settings > About Phone > Version to view the EMUI (Huawei) or Magic UI (Honor) version numberAffected if The installed version matches one of the affected versions: EMUI 8.0, 8.2, 9.1.0, 9.1.1, 10.0.0, 10.1.0, 10.1.1, 11.0.0 or Magic UI 2.1.1, 3.0.0, 3.1.0, 3.1.1, 4.0.0
-
Verify Samgr system service statusCheck if the Samgr service is active on the device; this is a core Huawei system service that manages system componentsAffected if The Samgr service is running and accessible, as the vulnerability allows denial of service against this critical component
-
Check installed security patchesIn Settings > About Phone > Software Info, view the security patch level date to determine if patches addressing this CVE have been appliedAffected if The device security patch level predates the availability of patches for CVE-2020-9158, indicating the cryptographic validation flaw remains unfixed
A user is affected if their device runs an unpatched EMUI or Magic UI version matching the affected version list, leaving the Samgr service vulnerable to denial of service via missing cryptographic validation.
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 dataApply available Huawei security patches for affected smartphone models; if no patch exists, monitor vendor advisories for updates addressing this cryptographic vulnerability.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9158 — 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-2020-9158 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