CVE-2017-8142
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 · uneditedThe Trusted Execution Environment (TEE) module driver of Mate 9 and Mate 9 Pro smart phones with software versions earlier than MHA-AL00BC00B221 and versions earlier than LON-AL00BC00B221 has a use after free (UAF) vulnerability. An attacker tricks a user into installing a malicious application, and the application can start multiple threads and try to create and free specific memory, which could triggers access memory after free it and causes a system crash or arbitrary 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 · high confidenceThe Trusted Execution Environment (TEE) module driver in Huawei Mate 9 and Mate 9 Pro smartphones contains a use-after-free vulnerability. A malicious application can start multiple threads to create and free specific memory regions, causing the driver to access memory after it has been freed, potentially resulting in system crash or arbitrary 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< mha-al00bc00b221< lon-al00bc00b221CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 Settings > About Phone on the device to confirm it is either Huawei Mate 9 or Huawei Mate 9 ProAffected if Device model is not Mate 9 or Mate 9 Pro - this CVE applies only to those specific models
-
Check Mate 9 firmware versionNavigate to Settings > About Phone > Build Number on the Mate 9 device to view the current firmware buildAffected if Firmware version is earlier than mha-al00bc00b221 (for Mate 9 model MHA-AL00)
-
Check Mate 9 Pro firmware versionNavigate to Settings > About Phone > Build Number on the Mate 9 Pro device to view the current firmware buildAffected if Firmware version is earlier than lon-al00bc00b221 (for Mate 9 Pro model LON-AL00)
-
Verify TEE driver presenceOn the affected device, check if the TEE driver module is loaded by examining /proc/modules or using a kernel log analysis toolAffected if TEE driver is present and loaded - exploitation requires the vulnerable TEE module driver to be active
The device is affected if it is a Huawei Mate 9 (MHA-AL00) with firmware before mha-al00bc00b221, or a Mate 9 Pro (LON-AL00) with firmware before lon-al00bc00b221, and the TEE driver module is loaded on the device.
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-AL00BC00B221 or later for Mate 9 (MHA-AL00), and LON-AL00BC00B221 or later for Mate 9 Pro (LON-AL00).
- Consultation3.0 h
- Implementation6.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8142 — 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-8142 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