CVE-2017-8210
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 driver of honor 5C,honor 6x Huawei smart phones with software of versions earlier than NEM-AL10C00B356, versions earlier than Berlin-L21HNC432B360 have a buffer overflow vulnerability due to the lack of parameter validation. An attacker tricks a user into installing a malicious APP which has the root privilege of the Android system, the APP can send a specific parameter to the driver of the smart phone, causing a system reboot 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 confidenceBuffer overflow vulnerability in the driver for Honor 5C and Honor 6x smartphones due to lack of parameter validation. A malicious application with root privileges can send specific parameters to the device driver, causing buffer overflow that leads to system reboot 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< nem-al10c00b356< berlin-l21hnc432b360CVSS 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.
-
Confirm device modelGo to Settings > About Phone or use 'getprop ro.product.name' via ADB to verify the device is Honor 5C (NEM-AL10) or Honor 6x (Berlin)Affected if Device model is not Honor 5C or Honor 6x
-
Check Honor 5C firmware versionGo to Settings > About Phone > Version or use 'getprop ro.build.version.emui' via ADB. Compare the build number to nem-al10c00b356Affected if Firmware version is less than nem-al10c00b356 on Honor 5C
-
Check Honor 6x firmware versionGo to Settings > About Phone > Version or use 'getprop ro.build.version.emui' via ADB. Compare the build number to berlin-l21hnc432b360Affected if Firmware version is less than berlin-l21hnc432b360 on Honor 6x
-
Verify driver module presenceCheck if the vulnerable device driver is loaded by examining /proc/modules or using 'lsmod' via ADB shell. The specific driver name would need to be identified from device drivers listAffected if Vulnerable driver module is present and loaded on the device
The device is affected if it is an Honor 5C with firmware below nem-al10c00b356 or an Honor 6x with firmware below berlin-l21hnc432b360, and the vulnerable driver is loaded.
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 dataApply the vendor firmware update: upgrade to NEM-AL10C00B356 or later for Honor 5C, and Berlin-L21HNC432B360 or later for Honor 6x. Since exploitation requires root-level access, ensure devices are not compromised prior to patching.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8210 — 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-8210 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