CVE-2019-5246
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 · uneditedSmartphones with software of ELLE-AL00B 9.1.0.109(C00E106R1P21), 9.1.0.113(C00E110R1P21), 9.1.0.125(C00E120R1P21), 9.1.0.135(C00E130R1P21), 9.1.0.153(C00E150R1P21), 9.1.0.155(C00E150R1P21), 9.1.0.162(C00E160R2P1) 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 DOS or 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 confidenceThe affected Huawei smartphones (ELLE-AL00B models running specific 9.1.0.x software versions) have an insufficient verification vulnerability where certain system parameters are not properly validated. An attacker with high-privilege access to the device can exploit this to cause denial of service or achieve malicious 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= 9.1.0.109\(c00e106r1p21\)= 9.1.0.113\(c00e110r1p21\)= 9.1.0.125\(c00e120r1p21\)= 9.1.0.135\(c00e130r1p21\)= 9.1.0.153\(c00e150r1p21\)= 9.1.0.155\(c00e150r1p21\)= 9.1.0.162\(c00e160r2p1\)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 device modelCheck the device model number in system settings under 'About Phone' or use 'getprop ro.product.model' via ADBAffected if model is not ELLE-AL00B or Elle Al00b, then not affected
-
Retrieve firmware versionAccess the build number or firmware version in Settings > About Phone > Version, or run 'getprop ro.build.version.emui' via ADB to get EMUI version detailsAffected if firmware version cannot be determined or does not match any of the listed affected versions, then not affected
-
Compare against affected versionsMatch your installed version string against: 9.1.0.109(c00e106r1p21), 9.1.0.113(c00e110r1p21), 9.1.0.125(c00e120r1p21), 9.1.0.135(c00e130r1p21), 9.1.0.153(c00e150r1p21), 9.1.0.155(c00e150r1p21), 9.1.0.162(c00e160r2p21)Affected if installed version exactly matches one of these seven versions, then the device is affected
The device is affected only if it is an ELLE-AL00B model running one of the seven specific firmware versions listed, and the attacker has high-privilege access to exploit the insufficient parameter validation.
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 the vendor-supplied firmware update to a patched version. Since the vulnerability requires high-privilege access, enforce access controls and restrict physical/logical access to trusted users only.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5246 — 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-5246 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