CVE-2020-9074
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 Smartphones HONOR 20 PRO;Honor View 20;HONOR 20 have an improper handling of exceptional condition Vulnerability. A component cannot deal with an exception correctly. Attackers can exploit this vulnerability by sending malformed message. This could compromise normal service of affected phones.
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 confidenceThe vulnerability exists in Huawei HONOR 20 PRO, Honor View 20, and HONOR 20 smartphones where a component fails to properly handle exceptional conditions. Attackers can exploit this by sending malformed messages to trigger improper exception handling, potentially compromising the normal service availability of the affected device.
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.194\(c432e9r5p1\)< 10.0.0.194\(c636e3r3p1\)< 10.0.0.194\(c00e62r8p12\)< 10.0.0.194\(c10e3r3p2\)< 10.0.0.200\(c185e3r3p3\)< 10.0.0.201\(c636e3r4p3\)< 10.0.0.195\(c00e62r4p11\)< 10.0.0.201\(c10e5r4p3\)< 10.0.0.186\(c185e2r2p1\)< 10.0.0.194\(c432e9r5p1\)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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
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 device modelCheck your phone settings under Settings > About Phone to confirm the exact model number is one of: HONOR 20 PRO, Honor View 20, or HONOR 20Affected if Device model is not one of these three models
-
Check firmware versionNavigate to Settings > About Phone > Version to view the installed build number (format like 10.0.0.194(c432e9r5p1))Affected if Unable to determine firmware version from settings
-
Compare Honor 20 Pro versionIf device is Honor 20 Pro, compare your build number against: 10.0.0.194(c432e9r5p1), 10.0.0.194(c636e3r3p1), 10.0.0.194(c00e62r8p12), or 10.0.0.194(c10e3r3p2)Affected if Installed version is lower than any of these four version strings
-
Compare Honor View 20 versionIf device is Honor View 20, compare your build number against: 10.0.0.200(c185e3r3p3), 10.0.0.201(c636e3r4p3), 10.0.0.195(c00e62r4p11), or 10.0.0.201(c10e5r4p3)Affected if Installed version is lower than any of these four version strings
-
Compare HONOR 20 versionIf device is HONOR 20, compare your build number against: 10.0.0.186(c185e2r2p1) or 10.0.0.194(c432e9r5p1)Affected if Installed version is lower than either of these two version strings
Device is affected if it is an Honor 20 Pro, View 20, or HONOR 20 running a firmware version lower than the specific build numbers listed for that model, as the vulnerability exists in those earlier versions due to improper exception handling.
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.18610.0.0.19410.0.0.195
Apply the vendor-provided security patch from Huawei/HONOR. Users should update their device firmware to the latest version containing the fix for improper exception handling.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9074 — 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-9074 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