CVE-2019-5227
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 · uneditedP30, P30 Pro, Mate 20 smartphones with software of versions earlier than ELLE-AL00B 9.1.0.193(C00E190R2P1), versions earlier than VOGUE-AL00A 9.1.0.193(C00E190R2P1), versions earlier than Hima-AL00B 9.1.0.135(C00E133R2P1) and HiSuite with versions earlier than HiSuite 9.1.0.305 have a version downgrade vulnerability. The device and HiSuite software do not validate the upgrade package sufficiently, so that the system of smartphone can be downgraded to an older version.
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 P30, P30 Pro, Mate 20 smartphones and HiSuite have insufficient validation of upgrade packages, allowing an attacker to downgrade the system to an older, potentially vulnerable version. This version downgrade vulnerability exploits the lack of integrity checks on firmware update packages.
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< elle-al00b_9.1.0.193\(c00e190r2p1\)< vogue-al00a_9.1.0.193\(c00e190r2p1\)< hima-al00b_9.1.0.135\(c00e133r2p1\)< 9.1.0.305CVSS 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.
-
Check Huawei P30 firmware versionGo to Settings > About Phone > Version on the P30 device. Note the build number (e.g., elle-al00b) and software version.Affected if Firmware version is lower than elle-al00b_9.1.0.193(C00E190R2P1)
-
Check Huawei P30 Pro firmware versionGo to Settings > About Phone > Version on the P30 Pro device. Note the build number (e.g., vogue-al00a) and software version.Affected if Firmware version is lower than vogue-al00a_9.1.0.193(C00E190R2P1)
-
Check Huawei Mate 20 firmware versionGo to Settings > About Phone > Version on the Mate 20 device. Note the build number (e.g., hima-al00b) and software version.Affected if Firmware version is lower than hima-al00b_9.1.0.135(C00E133R2P1)
-
Check HiSuite application versionOpen HiSuite, navigate to Settings or About section, or check the installed program version in Windows Add/Remove Programs.Affected if HiSuite version is lower than 9.1.0.305
If any of the four products (P30, P30 Pro, Mate 20, or HiSuite) have installed versions below their respective thresholds, the environment is affected by this downgrade vulnerability.
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 data9.1.0.305
Update device software to versions ELLE-AL00B 9.1.0.193(C00E190R2P1), VOGUE-AL00A 9.1.0.193(C00E190R2P1), Hima-AL00B 9.1.0.135(C00E133R2P1) and HiSuite to version 9.1.0.305 or later to obtain the fix.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5227 — 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-2019-5227 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