CVE-2020-9255
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 · uneditedHuawei Honor 10 smartphones with versions earlier than 10.0.0.178(C00E178R1P4) have a denial of service vulnerability. Certain service in the system does not sufficiently validate certain parameter which is received, the attacker should trick the user into installing a malicious application, successful exploit could cause a denial of service condition.
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 confidenceA denial of service vulnerability exists in Huawei Honor 10 smartphones where a system service fails to properly validate certain received parameters. An attacker must trick the user into installing a malicious application, which can then trigger the vulnerability and cause a denial of service condition.
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< 10.0.0.178\(c00e178r1p4\)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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.
-
Confirm device model is Honor 10Navigate to Settings > About Phone > Model Number (or Device Name) and verify the device is specifically Huawei Honor 10. Do not confuse with other Honor models or Huawei variants.Affected if Device model is Honor 10 and firmware version is below 10.0.0.178(c00e178r1p4)
-
Check firmware version numberNavigate to Settings > About Phone > Version. Record the displayed version number. Compare this against the affected range: any version less than 10.0.0.178(c00e178r1p4) is vulnerable.Affected if Installed firmware version is < 10.0.0.178(c00e178r1p4)
-
Check build numberNavigate to Settings > About Phone > Build Number. Verify the full build identifier includes c00e178r1p4 or a later version. Earlier build numbers indicate the vulnerable version.Affected if Build number does not contain c00e178r1p4 or a later build identifier
-
Review application installation policyCheck if the device has applications installed from unknown or untrusted sources. Go to Settings > Security > Unknown Sources (or Install unknown apps) to review permitted sources. The vulnerability requires a malicious app to be installed.Affected if Applications from untrusted sources are installed and firmware version is in the affected range
A user is affected if their Honor 10 runs firmware version below 10.0.0.178(c00e178r1p4) and has installed applications from untrusted sources that could trigger the vulnerable system service.
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 data10.0.0.178
Update Honor 10 devices to version 10.0.0.178(C00E178R1P4) or later via official Huawei/Honor firmware channels. Users should avoid installing applications from untrusted sources to prevent exploitation.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.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-2020-9255 — 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-9255 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