CVE-2019-5229
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 smartphones with versions earlier than ELLE-AL00B 9.1.0.193(C00E190R2P1) have an insufficient verification vulnerability. The system does not verify certain parameters sufficiently, an attacker should connect to the phone and gain high privilege to launch the attack, 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 · moderate confidenceInsufficient parameter verification in Huawei P30 smartphones (versions before ELLE-AL00B 9.1.0.193) allows authenticated attackers with high privilege to execute malicious code by connecting to the device and exploiting unchecked parameters.
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
- Physical
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:H/UI:N/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 the device modelCheck if the target device is a Huawei P30 smartphone. This can be done by checking the device settings under 'Settings' > 'About Phone' > 'Model' or by examining the device packaging or system information.Affected if Device is not a Huawei P30 (the vulnerability only affects this specific model)
-
Retrieve the firmware versionNavigate to 'Settings' > 'About Phone' > 'Version' on the Huawei P30 device to display the current firmware build number. Alternatively, use the command 'AT^VERSION=' or check the build.prop file at /system/build.prop for the 'ro.build.display.id' or 'ro.sw.version' property.Affected if Unable to retrieve a firmware version from the device
-
Compare firmware version against affected rangeExamine the firmware version string obtained from the previous step. The affected version range is any version before 'elle-al00b_9.1.0.193(c00e190r2p1)'. Compare your version string numerically and alphanumerically against this threshold.Affected if Firmware version is lower than elle-al00b_9.1.0.193 (for example, 9.1.0.150, 9.0.0.200, etc.) - this indicates the device is vulnerable
-
Verify high-privilege access capabilityThe vulnerability requires an authenticated attacker with high privilege to connect to the device and exploit unchecked parameters. Check if the device has debugging enabled (Settings > Developer Options > USB debugging) or if there are any exposed services accepting remote connections that could allow authenticated access.Affected if Device has USB debugging enabled or exposed network services that could allow an authenticated high-privilege attacker to connect and exploit unchecked parameters
The device is affected if it is a Huawei P30 running firmware version lower than elle-al00b_9.1.0.193(c00e190r2p1) and has the potential for an authenticated high-privilege attacker to connect and exploit unchecked parameters.
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 P30 devices to firmware version ELLE-AL00B 9.1.0.193(C00E190R2P1) or later to remediate the insufficient verification vulnerability.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5229 — 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-5229 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