dbcve.org
Gt3 FirmwareOperating system · Huawei

CVE-2017-2697

HIGH · 7.8 CVSS v3.0 Published 2017-11-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
The goldeneye driver in NMO-L31C432B120 and earlier versions,NEM-L21C432B100 and earlier versions,NEM-L51C432B120 and earlier versions,KNT-AL10C746B160 and earlier versions,VNS-L21C185B142 and earlier versions,CAM-L21C10B130 and earlier versions,CAM-L21C185B141 and earlier versions has buffer overflow vulnerability. An attacker with the root privilege of the Android system can tricks a user into installing a malicious application on the smart phone, and send given parameter to smart phone to crash the system or escalate privilege.

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 confidence

Buffer overflow vulnerability in the goldeneye kernel driver affecting multiple Huawei Android devices. An attacker with existing root privileges can send a crafted parameter via a malicious application to trigger the overflow, causing system crash or privilege escalation to potentially compromise the kernel.

MitigationApply vendor-supplied firmware updates from Huawei for affected models; until patch is available, restrict installation of untrusted applications and monitor for Indicators of Compromise.

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
Gt3 FirmwareOperating system
Affected:<= nmo-l31c432b120
Honor 5c FirmwareOperating system
Affected:<= nem-l51c432b120
Knt FirmwareOperating system
Affected:<= knt-al10c746b160
P9 Lite FirmwareOperating system
Affected:<= vns-l21c185b142
Y6ii FirmwareOperating system
Affected:<= cam-l21c10b130<= cam-l21c185b141

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Check the device settings or use 'getprop ro.product.model' to confirm the exact Huawei model
    Affected if Model is not one of: Huawei Gt3, Honor 5c, Knt, P9 Lite, or Y6ii (the vulnerability only affects these specific models)
  2. Check firmware version for Gt3
    Run 'getprop ro.build.version.emui' or check Settings > About Phone > Version for the nmo-l31 firmware build number
    Affected if Firmware build is nmo-l31c432b120 or earlier (any version <= nmo-l31c432b120)
  3. Check firmware version for Honor 5c
    Run 'getprop ro.build.version.emui' or check Settings > About Phone > Version for the nem-l51 firmware build number
    Affected if Firmware build is nem-l51c432b120 or earlier (any version <= nem-l51c432b120)
  4. Check firmware version for Knt
    Run 'getprop ro.build.version.emui' or check Settings > About Phone > Version for the knt-al10 firmware build number
    Affected if Firmware build is knt-al10c746b160 or earlier (any version <= knt-al10c746b160)
  5. Check firmware version for P9 Lite
    Run 'getprop ro.build.version.emui' or check Settings > About Phone > Version for the vns-l21 firmware build number
    Affected if Firmware build is vns-l21c185b142 or earlier (any version <= vns-l21c185b142)
  6. Check firmware version for Y6ii
    Run 'getprop ro.build.version.emui' or check Settings > About Phone > Version for the cam-l21 firmware build number
    Affected if Firmware build is cam-l21c10b130 or earlier, OR cam-l21c185b141 or earlier (any version <= cam-l21c10b130 or <= cam-l21c185b141)

The device is affected only if it is one of the listed Huawei models AND its firmware version falls within or below the specified build numbers for that model, since the buffer overflow exists in the goldeneye kernel driver of those specific firmware versions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates from Huawei for affected models; until patch is available, restrict installation of untrusted applications and monitor for Indicators of Compromise.

Fix this in Gt3 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-2697 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-2697 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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