CVE-2017-17140
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 Enjoy 5s and Y6 Pro smartphones with software the versions before TAG-AL00C92B170; the versions before TIT-L01C576B121 have an information leak vulnerability due to the lack of parameter validation. An attacker tricks a user into installing a malicious application on the smart phone and the application can read some sensitive information in kernel memory 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 confidenceThis is a local information disclosure vulnerability in Huawei Enjoy 5s and Y6 Pro smartphones. The lack of parameter validation in the kernel allows a malicious application installed by the user to read sensitive information directly from kernel memory.
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< tag-al00c92b170< tit-l01c576b121CVSS 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 the device model in Settings > About Phone to confirm it is a Huawei Enjoy 5s or Y6 ProAffected if The device model is Huawei Enjoy 5s or Huawei Y6 Pro
-
Locate the firmware versionNavigate to Settings > About Phone > Version on the Huawei device and record the Build Number or Firmware version displayedAffected if The device is an Enjoy 5s or Y6 Pro model
-
Compare Enjoy 5s firmware against thresholdFor Enjoy 5s models, compare the installed Build Number to tag-al00c92b170 - note that version strings are alphanumeric and may not sort numericallyAffected if The Build Number is alphabetically lower than tag-al00c92b170 (e.g., tag-al00c91xxx or earlier)
-
Compare Y6 Pro firmware against thresholdFor Y6 Pro models, compare the installed Build Number to tit-l01c576b121 - note that version strings are alphanumeric and may not sort numericallyAffected if The Build Number is alphabetically lower than tit-l01c576b121 (e.g., tit-l01c575xxx or earlier)
-
Verify kernel access vulnerability potentialThe vulnerability allows a malicious application to read kernel memory due to missing parameter validation in the kernel - this is a kernel-level flaw, not a configuration setting that can be checked manuallyAffected if The firmware version is below the patched thresholds for either model - no manual kernel inspection is feasible for end users
A user is affected if they have a Huawei Enjoy 5s with Build Number below tag-al00c92b170, or a Huawei Y6 Pro with Build Number below tit-l01c576b121.
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 software to version TAG-AL00C92B170 or later (Enjoy 5s) or TIT-L01C576B121 or later (Y6 Pro), and only install applications from trusted sources.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,312.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17140 — 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-17140 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