CVE-2017-17139
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 · uneditedHuawei Mate 9 and Mate 9 pro smart phones with software the versions before MHA-AL00B 8.0.0.334(C00); the versions before LON-AL00B 8.0.0.334(C00) have a information leak vulnerability in the date service proxy implementation. An attacker may trick a user into installing a malicious application and application can exploit the vulnerability to get kernel date 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 confidenceThe vulnerability exists in the date service proxy implementation on Huawei Mate 9 and Mate 9 Pro smartphones running software versions prior to MHA-AL00B 8.0.0.334(C00) and LON-AL00B 8.0.0.334(C00). A malicious application installed on the device can exploit this flaw to access kernel date information, potentially exposing sensitive system 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-al00b_8.0.0.334\(c00\)< mha-al00b_8.0.0.334\(c00\)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.
-
Identify the device modelCheck if the device is a Huawei Mate 9 (MHA-AL00) or Mate 9 Pro (LON-AL00) by going to Settings > About Phone > Model NumberAffected if The device is a Huawei Mate 9 or Mate 9 Pro
-
Retrieve the firmware versionNavigate to Settings > About Phone > Version > Build Number or use the command 'getprop ro.build.version.emui' via ADB shell to retrieve the exact firmware buildAffected if The firmware version cannot be determined or is below the threshold
-
Compare against affected version rangesFor Mate 9 (MHA-AL00), verify if version is less than 8.0.0.334(C00). For Mate 9 Pro (LON-AL00), verify if version is less than 8.0.0.334(C00)Affected if The installed firmware version is lower than 8.0.0.334(C00) for the respective model
-
Confirm the date service proxy is presentCheck if the date service proxy component exists on the device (typically in /system/bin/ or as a system service). This varies by implementation and may require root access to inspectAffected if The vulnerable date service proxy component is present on the device
The device is affected if it is a Huawei Mate 9 (MHA-AL00) or Mate 9 Pro (LON-AL00) running firmware version lower than 8.0.0.334(C00) with the date service proxy component 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 dataUpdate the device firmware to version MHA-AL00B 8.0.0.334(C00) or LON-AL00B 8.0.0.334(C00) or later. Users should only install applications from trusted sources to mitigate this and similar vulnerabilities.
- Consultation1.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-2017-17139 — 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-2017-17139 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