CVE-2019-5212
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 · uneditedThere is an improper access control vulnerability in Huawei Share. The software does not properly restrict access to certain file from certain application. An attacker tricks the user into installing a malicious application then establishing a connect to the attacker through Huawei Share, successful exploit could cause information disclosure.
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 confidenceHuawei Share has an improper access control vulnerability where the software fails to properly restrict file access between certain applications. An attacker must trick the user into installing a malicious application, which then can establish a connection through Huawei Share to access sensitive files that should be protected, leading to information disclosure.
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< emily-l29c_9.1.0.311\(c10e2r1p13t8\)< emily-l29c_9.1.0.311\(c461e2r1p11t8\)< emily-l29c_9.1.0.311\(c605e2r1p12t8\)< emily-l29c_9.1.0.311\(c432e7r1p11t8\)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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/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.
-
Identify Huawei P20 device modelCheck device model number in Settings > About Phone. Look for 'P20' or 'emily-l29c' model identifier.Affected if Device is not a Huawei P20 (emily-l29c variant)
-
Check firmware build numberNavigate to Settings > About Phone > Version. Record the full build number displayed (e.g., emily-l29c_9.1.0.311(c10e2r1p13t8)).Affected if Build number is lower than any of the affected version strings (9.1.0.311 with any of the specified build tags)
-
Verify Huawei Share feature statusCheck if Huawei Share is enabled: Open Settings > Huawei Share (or search 'Huawei Share' in settings). Note whether the feature toggle is turned on or if the feature exists on the device.Affected if Huawei Share is enabled or available on the device - the vulnerability requires this feature to be present to exploit
-
Compare against all affected version patternsCompare your full build string against all four affected variants: c10e2r1p13t8, c461e2r1p11t8, c605e2r1p12t8, c432e7r1p11t8. Any build below 9.1.0.311 with these specific build tags is affected.Affected if Your firmware version is 9.1.0.311 with any of the listed build tags OR any version lower than 9.1.0.311 on emily-l29c
Device is affected if it is a Huawei P20 (emily-l29c) running firmware below 9.1.0.311 and Huawei Share feature is present and enabled.
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-supplied patches for affected Huawei devices running Huawei Share. Users should avoid installing applications from untrusted sources to prevent the initial malicious app installation required for exploitation.
- Consultation4.0 h
- Testing6.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 $3,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5212 — 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-5212 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