CVE-2020-9076
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 P30;HUAWEI P30 Pro;Tony-AL00B smartphones with versions earlier than 10.1.0.135(C00E135R2P11); versions earlier than 10.1.0.135(C00E135R2P8), versions earlier than 10.1.0.135 have an improper authentication vulnerability. Due to the identity of the message sender not being properly verified, an attacker can exploit this vulnerability through man-in-the-middle attack to induce user to access malicious URL.
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 · high confidenceThe affected Huawei P30 and P30 Pro smartphones have an improper authentication vulnerability in message handling where sender identity is not properly verified. An attacker positioned as a man-in-the-middle can intercept and modify messages to induce users to access malicious URLs.
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.1.0.135\(c00e135r2p11\)< 10.1.0.135\(c00e135r2p8\)< 10.1.0.135\(c01e135r2p8\)< 10.1.0.137\(c00e137r2p11\)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
- High
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
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 modelGo to Settings > About Phone and verify the model number is Huawei P30, P30 Pro, or Tony-AL00bAffected if Device model matches one of the affected models (P30, P30 Pro, or Tony-AL00b)
-
Check firmware version for P30Go to Settings > About Phone > Version and note the build number (e.g., 10.1.0.135(c00e135r2p11))Affected if Firmware version is lower than 10.1.0.135(c00e135r2p11) on a Huawei P30
-
Check firmware version for P30 ProGo to Settings > About Phone > Version and note the build number (e.g., 10.1.0.135(c00e135r2p8) or c01e135r2p8)Affected if Firmware version is lower than 10.1.0.135(c00e135r2p8) or 10.1.0.135(c01e135r2p8) on a Huawei P30 Pro
-
Check firmware version for Tony-AL00bGo to Settings > About Phone > Version and note the build number (e.g., 10.1.0.137(c00e137r2p11))Affected if Firmware version is lower than 10.1.0.137(c00e137r2p11) on a Huawei Tony-AL00b
User is affected if they own a Huawei P30, P30 Pro, or Tony-AL00b device running firmware version below the specific threshold for their model.
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.1.0.13510.1.0.137
Update smartphone firmware to version 10.1.0.135 or later (specific to model variant: C00E135R2P11 for Tony-AL00B, C00E135R2P8 for others) to remediate the vulnerability.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.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,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9076 — 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-9076 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