CVE-2020-9226
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 with versions earlier than 10.1.0.135(C00E135R2P11) have an improper signature verification vulnerability. The system does not improper check signature of specific software package, an attacker may exploit this vulnerability to load a crafted software package to the device.
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 Huawei P30 has an improper signature verification vulnerability where the system does not properly check the signature of a specific software package. This allows an attacker to load a crafted software package onto the device by exploiting the lack of cryptographic verification in the package loading process.
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\)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
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Verify device model is Huawei P30Go to Settings > About Phone > Model Number and confirm it shows Huawei P30 or any variant (like ELE-L29, ELE-AL00, etc.)Affected if The device model is not a Huawei P30 - this vulnerability only affects that specific model
-
Check the current firmware versionGo to Settings > About Phone > Version and locate the build number or firmware version displayed (typically shows as something like 10.1.0.xxx)Affected if Unable to determine the firmware version from the device settings
-
Compare firmware version against the affected rangeCompare the installed firmware version number (the numeric portion before the parentheses) to 10.1.0.135 - any version below 10.1.0.135 is affectedAffected if The firmware version is below 10.1.0.135 (for example, 10.0.1.120 or 9.1.0.95) - this indicates the signature verification vulnerability is present
-
Confirm full build number if version appears close to thresholdIf the version shows 10.1.0.1xx, check the full build identifier in Settings > About Phone > Build Number to see the complete version string including the parentheses portion (for example, c00e135r2p11)Affected if The full build string is earlier than c00e135r2p11 in version 10.1.0.1xx, indicating the patch is not applied
You are affected if your Huawei P30 runs firmware version 10.1.0.135 or any version below that threshold.
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.135
Update Huawei P30 to version 10.1.0.135(C00E135R2P11) or later, which contains the proper signature verification fix. Avoid loading software packages from untrusted sources.
- 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-9226 — 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-9226 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