CVE-2017-8184
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 · uneditedMTK platform in Huawei smart phones with software of earlier than Nice-AL00C00B160 versions, earlier than Nice-AL10C00B140 versions has a any memory access vulnerability. An attacker tricks a user into installing a malicious application on the smart phone, and send given parameter to cause to any memory access vulnerabilities, leading to sensitive information leakage.
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 confidenceA memory access vulnerability exists in the MTK platform of Huawei smartphones running software versions prior to Nice-AL00C00B160 or Nice-AL10C00B140. An attacker can trick a user into installing a malicious application that sends specific parameters to trigger arbitrary memory access, leading to sensitive information leakage.
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< nice-al10c00b140< nice-al00c00b160CVSS 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 device model and platformCheck the phone settings to confirm the device is a Huawei smartphone using the MTK (MediaTek) platform chipset. This is typically visible under Settings > About Phone > Chipset or Processor information.Affected if The device uses an MTK platform chipset from Huawei
-
Check firmware version for Nice-AL10Navigate to Settings > About Phone > Software Info and locate the build number or version string. For Nice-AL10 models, note the full version identifier.Affected if The installed version is lower than nice-al10c00b140 (e.g., nice-al10c00b130, nice-al10b, etc.)
-
Check firmware version for Nice-AL00Navigate to Settings > About Phone > Software Info and locate the build number or version string. For Nice-AL00 models, note the full version identifier.Affected if The installed version is lower than nice-al00c00b160 (e.g., nice-al00c00b150, nice-al00b, etc.)
-
Confirm malicious app exposureReview installed applications and verify if any untrusted or recently installed third-party applications have unusual permissions, particularly those requesting access to system services or sensitive data.Affected if A malicious application with elevated permissions is installed that could send specific parameters to trigger the memory access vulnerability
The device is affected if it is a Huawei phone with MTK platform running Nice-AL10 firmware below nice-al10c00b140 or Nice-AL00 firmware below nice-al00c00b160, and a malicious application could exploit the arbitrary memory access to leak sensitive information.
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 dataUpgrade affected Huawei smartphones running Nice-AL00 and Nice-AL10 software to version Nice-AL00C00B160 or later and Nice-AL10C00B140 or later respectively, via official OTA or manual firmware update methods.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8184 — 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-8184 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