CVE-2019-5244
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 · uneditedMate 9 Pro Huawei smartphones earlier than LON-L29C 8.0.0.361(C636) versions have an information leak vulnerability due to the lack of input validation. An attacker tricks the user who has root privilege to install an application on the smart phone, and the application can read some process information, which may cause sensitive information leak.
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 confidenceInformation leak vulnerability in Huawei Mate 9 Pro smartphones prior to version LON-L29C 8.0.0.361(C636) due to lack of input validation. A malicious application with root privileges can read process information, potentially exposing sensitive data.
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< lon-l29c_8.0.0.361\(c636\)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.0/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.
-
Confirm device model is Huawei Mate 9 ProGo to Settings > About Phone > Model Number (or Device Name) and verify it shows 'Mate 9 Pro' or a similar variant identifierAffected if Device model is anything other than Huawei Mate 9 Pro - this vulnerability only affects that specific model
-
Check firmware version installedGo to Settings > About Phone > Version. Look for the build number or firmware version string (typically displayed as LON-Lxx or similar)Affected if You cannot determine the firmware version from your device settings
-
Compare installed version to vulnerable rangeIf your version shows LON-L29C, verify the full version number is below 8.0.0.361(C636). Check Settings > About Phone > Build Number for the complete version stringAffected if Firmware version is LON-L29C 8.0.0.361(C636) or higher - these versions include the input validation fix
-
Verify if device has root accessCheck if a root management app (such as SuperSU, Magisk) is installed or if root is indicated in yourAbout Phone settingsAffected if Device does NOT have root privileges - the vulnerability requires a malicious app with root privileges to exploit it; unrooted devices face lower risk from this specific flaw
You are affected if you own a Huawei Mate 9 Pro with firmware version LON-L29C below 8.0.0.361(C636) and your device has root privileges or could potentially install a malicious root-privileged application.
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 Huawei Mate 9 Pro devices to firmware version LON-L29C 8.0.0.361(C636) or later to patch the input validation vulnerability.
- 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-5244 — 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-5244 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