CVE-2017-2726
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 · uneditedBastet in P10 Plus and P10 smart phones with software earlier than VKY-AL00C00B123 versions, earlier than VTR-AL00C00B123 versions have a buffer overflow vulnerability. An attacker with the root privilege of an Android system may trick a user into installing a malicious APP. The APP can modify specific data to cause buffer overflow in the next system reboot, causing continuous 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 Huawei P10/P10 Plus smartphones running software versions earlier than VKY-AL00C00B123 and VTR-AL00C00B123. An attacker with Android root privileges can use a malicious app to modify specific system data that triggers a buffer overflow on next reboot, causing continuous reboots 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< vtr-al00c00b123< vky-al00c00b123CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:N/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 the device modelCheck the device settings or boot screen to confirm whether the device is a Huawei P10 or Huawei P10 PlusAffected if The device model is Huawei P10 or Huawei P10 Plus
-
Check the installed firmware versionNavigate to Settings > About Phone on the Huawei device to view the current firmware/build numberAffected if The firmware version cannot be determined or is not visible
-
Compare firmware version for Huawei P10If the device is Huawei P10, compare the installed version (such as VTR-AL00xxx) against the affected threshold VTR-AL00C00B123Affected if The installed VTR-AL00 version is less than C00B123 (for example, VTR-AL00xx earlier than VTR-AL00C00B123)
-
Compare firmware version for Huawei P10 PlusIf the device is Huawei P10 Plus, compare the installed version (such as VKY-AL00xxx) against the affected threshold VKY-AL00C00B123Affected if The installed VKY-AL00 version is less than C00B123 (for example, VKY-AL00xx earlier than VKY-AL00C00B123)
-
Assess root privilege exposureDetermine whether the device has been rooted or if applications with root privileges are present, as the attacker requires Android root privileges to exploit this flawAffected if The device has root access enabled or unknown third-party apps have root permissions
The device is affected if it is a Huawei P10 with firmware version earlier than VTR-AL00C00B123, or a Huawei P10 Plus with firmware version earlier than VKY-AL00C00B123, and the device has root privileges or exposure to a malicious root-privileged app.
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 vendor firmware update VKY-AL00C00B123 (or later) for P10 Plus and VTR-AL00C00B123 (or later) for P10 to patch the vulnerability. Organizations should inventory affected devices and push firmware updates through MDM or direct deployment.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2726 — 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-2726 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