CVE-2017-8211
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 confidenceA buffer overflow vulnerability exists in the kernel driver for Honor 5C and Honor 6X smartphones due to insufficient parameter validation. A malicious Android application with root privileges can send specific parameters to the vulnerable driver, triggering the overflow and causing either system reboot or arbitrary code execution with kernel-level privileges.
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.
-
Identify device modelCheck device model number in Settings > About Phone. Look for NEM-AL10 (Honor 5C) or Berlin-L21 (Honor 6X).Affected if Device is not Honor 5C (NEM-AL10) or Honor 6X (Berlin-L21) - not affected.
-
Check firmware version on Honor 5CFor NEM-AL10 devices, go to Settings > About Phone > Version and compare the build number to nem-al10c00b356. On device, run: getprop ro.build.display.idAffected if Firmware version is less than nem-al10c00b356 on NEM-AL10 - potentially affected.
-
Check firmware version on Honor 6XFor Berlin-L21 devices, go to Settings > About Phone > Version and compare the build number to berlin-l21hnc432b360. On device, run: getprop ro.build.display.idAffected if Firmware version is less than berlin-l21hnc432b360 on Berlin-L21 - potentially affected.
-
Verify kernel driver presenceCheck if the vulnerable kernel driver module is loaded. Run: lsmod | grep -i <driver_name> or check /proc/modules. Note: The specific driver name is not disclosed in the advisory.Affected if Driver is present and loaded on an affected firmware version - likely vulnerable.
Device is affected only if it is an Honor 5C (NEM-AL10) or Honor 6X (Berlin-L21) running firmware below the specified thresholds AND the vulnerable kernel 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 dataUpdate the device firmware to a version newer than NEM-AL10C00B356 for NEM-AL10 and Berlin-L21HNC432B360 for Berlin-L21 to receive the vendor patch that adds proper parameter validation to the driver.
- Consultation4.0 h
- Implementation16.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8211 — 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-8211 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