CVE-2019-5228
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 · uneditedCertain detection module of P30, P30 Pro, Honor V20 smartphone whith Versions earlier than ELLE-AL00B 9.1.0.193(C00E190R1P21), Versions earlier than VOGUE-AL00A 9.1.0.193(C00E190R1P12), Versions earlier than Princeton-AL10B 9.1.0.233(C00E233R4P3) have a race condition vulnerability. The system does not lock certain function properly, when the function is called by multiple processes could cause out of bound write. An attacker tricks the user into installing a malicious application, successful exploit could cause malicious code execution.
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 confidenceRace condition in Huawei smartphone detection module. The system fails to properly lock a function, allowing multiple processes to simultaneously call it, causing an out-of-bounds write vulnerability. Exploitation requires user to install a malicious application, enabling arbitrary code execution.
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\(c00e190r1p21\)< vogue-al00a_9.1.0.193\(c00e190r1p12\)< princeton-al10b_9.1.0.233\(c00e233r4p3\)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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 your device modelCheck the device settings - typically found under Settings > About Phone > Model numberAffected if Device is not a Huawei P30, P30 Pro, or Honor V20 (not affected)
-
Check Huawei P30 firmware versionGo to Settings > About Phone > Version. Compare the build number to elle-al00b_9.1.0.193(c00e190r1p21)Affected if Firmware version is lower than elle-al00b_9.1.0.193(c00e190r1p21)
-
Check Huawei P30 Pro firmware versionGo to Settings > About Phone > Version. Compare the build number to vogue-al00a_9.1.0.193(c00e190r1p12)Affected if Firmware version is lower than vogue-al00a_9.1.0.193(c00e190r1p12)
-
Check Honor V20 firmware versionGo to Settings > About Phone > Version. Compare the build number to princeton-al10b_9.1.0.233(c00e233r4p3)Affected if Firmware version is lower than princeton-al10b_9.1.0.233(c00e233r4p3)
-
Review installed applicationsGo to Settings > Apps > App manager. Look for any applications installed from untrusted or unknown sourcesAffected if Malicious applications are present on the device (required for exploitation)
Device is affected if it is a Huawei P30, P30 Pro, or Honor V20 running firmware below the specified version AND has a malicious application installed.
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 dataUpdate affected devices (P30, P30 Pro, Honor V20) to the specified versions or later. Avoid installing applications from untrusted sources.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5228 — 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-5228 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