CVE-2019-5287
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 smart phones with versions earlier than ELLE-AL00B 9.1.0.193(C00E190R2P1) have an integer overflow vulnerability due to insufficient check on specific parameters. An attacker tricks the user into installing a malicious application, obtains the root permission and constructs specific parameters to the camera program to exploit this vulnerability. Successful exploit could cause the program to break down or allow for arbitrary 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 · moderate confidenceInteger overflow vulnerability in the camera program of Huawei P30 smartphones running firmware versions earlier than ELLE-AL00B 9.1.0.193(C00E190R2P1). The vulnerability stems from insufficient validation of specific parameters, allowing an attacker who has already obtained root privileges to send crafted input to the camera service, triggering the overflow and potentially causing denial of service or 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\(c00e190r2p1\)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.
-
Confirm device model is Huawei P30Go to Settings > About Phone > Model Number, or run 'getprop ro.product.model' via ADB/shellAffected if Model is not Huawei P30 (the vulnerability only affects this specific model)
-
Check firmware version/build numberGo to Settings > About Phone > Version > Build Number, or run 'getprop ro.build.version.emui' and 'getprop ro.build.display.id' via ADB/shellAffected if Build number is earlier than ELLE-AL00B 9.1.0.193(C00E190R2P1) or cannot be determined to be that version or later
-
Verify camera service is accessibleAttempt to open the camera application, or run 'dumpsys camera' via ADB/shell to confirm camera service is activeAffected if Camera service is running and accessible (the overflow triggers when crafted input is sent to this service)
-
Confirm root privilege statusCheck if the device has been rooted (e.g., presence of SuperSU, Magisk, or 'su' binary in common paths, or 'id' command showing uid=0)Affected if Root privileges are present on the device - the advisory states the attacker must already have root to exploit this vulnerability
User is affected if they are on a Huawei P30 with firmware earlier than ELLE-AL00B 9.1.0.193(C00E190R2P1) and the device has been rooted, since the attacker requires root privileges to trigger the integer overflow in the camera service.
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 dataApply vendor firmware update ELLE-AL00B 9.1.0.193(C00E190R2P1) or later to patched camera component. Restrict installation of applications from untrusted sources and revoke unnecessary root privileges to limit attack surface.
- 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-2019-5287 — 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-5287 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