CVE-2020-9095
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 Pro smartphone with Versions earlier than 10.1.0.160(C00E160R2P8) has an integer overflow vulnerability. Some functions are lack of verification when they process some messages sent from other module. Attackers can exploit this vulnerability by send malicious message to cause integer overflow. This can compromise normal service.
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 confidenceInteger overflow vulnerability in HUAWEI P30 Pro smartphone message processing functions. Certain functions lack proper validation when processing messages from other modules, allowing attackers to send malicious messages that trigger integer overflow and compromise normal device service.
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.160\(c00e160r2p8\)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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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 device modelGo to Settings > About Phone > Model Number on the device and verify it shows 'Huawei P30 Pro' or 'LIO-AL00' / 'LIO-TL00' (regional variants)Affected if Device model is not Huawei P30 Pro - the device is not affected by this specific CVE
-
Check firmware version numberGo to Settings > About Phone > Version > Build Number or Settings > System > Software Info > Version Number. Look for a version string like '10.1.0.160' or earlierAffected if The version number displayed is less than 10.1.0.160 - the device may be affected
-
Verify full build identifierCheck Settings > About Phone > Version > C00E160R2P8 (the build number in parentheses from the affected range). The complete version string typically appears as '10.1.0.160(C00E160R2P8)' or similarAffected if Build number is earlier than C00E160R2P8 or the version string contains a build identifier lower than r2p8 in the sequence
-
Confirm message processing exposureThis vulnerability affects message processing functions receiving input from other modules. If the device receives messages from external sources or inter-process communication from other apps/services, the integer overflow condition could be triggeredAffected if Device processes messages from other modules and version is below 10.1.0.160
A user is affected only if they are using a Huawei P30 Pro with firmware version below 10.1.0.160(C00E160R2P8) and the device processes messages from other modules.
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.160
Update HUAWEI P30 Pro to version 10.1.0.160(C00E160R2P8) or later via system software update. For enterprise environments, deploy updates through mobile device management (MDM) solutions.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-9095 — 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-9095 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