CVE-2017-8149
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 boot loaders of P10 and P10 Plus Huawei mobile phones with software the versions before Victoria-L09AC605B162, the versions before Victoria-L29AC605B162, the versions before Vicky-L29AC605B162 have an out-of-bounds memory access vulnerability due to the lack of parameter validation. 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 out-of-bounds memory read which can continuous system reboot.
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 confidenceThe bootloader in Huawei P10/P10 Plus mobile phones lacks parameter validation, allowing a malicious app with root privileges to modify specific data that triggers a buffer overflow on system reboot. This causes out-of-bounds memory read, resulting in continuous system reboot (denial of service).
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< victoria-l09ac605b162< victoria-l29ac605b162< vicky-l29ac605b162CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 model is Huawei P10 or P10 PlusGo to Settings > About Phone > Model Number, or run 'getprop ro.product.model' via ADB shell or terminal emulatorAffected if Model number is not Huawei P10 (vicky-l09/vicky-l29) or Huawei P10 Plus (vicky-l29) - different models are not affected
-
Identify the exact firmware versionGo to Settings > About Phone > Version, or run 'getprop ro.build.display.id' via ADB shell or terminal emulatorAffected if Firmware version is earlier than victoria-l09ac605b162 or victoria-l29ac605b162 for P10, or earlier than vicky-l29ac605b162 for P10 Plus
-
Check for root access presenceRun 'su' command in terminal or check for root management apps (SuperSU, Magisk). If the device has never been rooted, the exploit cannot be executedAffected if Device has root privileges - a malicious app with root access is required to trigger the vulnerability
-
Verify bootloader version and lock statusReboot to fastboot mode (power + volume down) and run 'fastboot oem version' or check Settings > Developer options > OEM unlocking statusAffected if Bootloader is unlocked or modified, which may indicate the device has been exposed to root-level modifications
Device is affected only if it is a Huawei P10 or P10 Plus with firmware version below the patched releases AND has root privileges available to a malicious 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 the vendor firmware update (Victoria-L09AC605B162 or later for P10, Victoria-L29AC605B162 or later for P10 Plus, Vicky-L29AC605B162 or later for P10 Plus variant) to patch the bootloader parameter validation vulnerability.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8149 — 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-8149 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