dbcve.org
P10 FirmwareOperating system · Huawei

CVE-2017-8150

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 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 arbitrary memory write 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 arbitrary memory writing 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 confidence

The boot loaders of Huawei P10 and P10 Plus phones contain an arbitrary memory write vulnerability due to lack of parameter validation. A malicious application with root privileges can modify specific data that persists across reboots, causing the bootloader to write to arbitrary memory locations during the next boot cycle, leading to continuous reboots or arbitrary code execution.

MitigationUpdate affected Huawei P10/P10 Plus devices to software versions Victoria-L09AC605B162 or later for the P10, and Victoria-L29AC605B162/Vicky-L29AC605B162 or later for the P10 Plus. Avoid installing applications from untrusted sources.

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
P10 FirmwareOperating system
Affected:< victoria-l09ac605b162< victoria-l29ac605b162
P10 Plus FirmwareOperating system
Affected:< vicky-l29ac605b162
P8 Lite FirmwareOperating system
Affected:< ale-l21c113b566
P9 FirmwareOperating system
Affected:< eva-l09c432b391< eva-l09c576b386< eva-l09c605b390< eva-l09c635b387< eva-l09c636b388< eva-l19c10b390< eva-l19c432b388< eva-l19c605b390< eva-l19c636b391

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 phone model number in Settings > About Phone. Affected models are Huawei P10, P10 Plus, P8 Lite, and P9.
    Affected if Device is not one of these four models - not affected
  2. Check P10 firmware version
    On Huawei P10, go to Settings > About Phone > Version. Look for the build number containing 'victoria-l09' or 'victoria-l29'. Compare the suffix after 'ac605b' to 162 (for example, victoria-l09ac605b162 is fixed).
    Affected if Version is victoria-l09ac605b161 or lower, or victoria-l29ac605b161 or lower
  3. Check P10 Plus firmware version
    On Huawei P10 Plus, go to Settings > About Phone > Version. Look for the build number containing 'vicky-l29'. Compare the suffix after 'ac605b' to 162.
    Affected if Version is vicky-l29ac605b161 or lower
  4. Check P8 Lite firmware version
    On Huawei P8 Lite, go to Settings > About Phone > Version. Look for the build number containing 'ale-l21'. Compare the suffix after 'c113b' to 566.
    Affected if Version is ale-l21c113b565 or lower
  5. Check P9 firmware version
    On Huawei P9, go to Settings > About Phone > Version. Look for build numbers starting with 'eva-l09', 'eva-l19', or 'eva-l19'. Compare the numeric suffixes to the affected thresholds: c432b391, c576b386, c605b390, c635b387, c636b388, c10b390, c432b388, c605b390, c636b391.
    Affected if Version falls below any of these thresholds for the respective build variant

The device is affected if it is a Huawei P10, P10 Plus, P8 Lite, or P9 running firmware version lower than the specified thresholds, and a malicious root-level application has had opportunity to persist modified data across reboots.

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

Update affected Huawei P10/P10 Plus devices to software versions Victoria-L09AC605B162 or later for the P10, and Victoria-L29AC605B162/Vicky-L29AC605B162 or later for the P10 Plus. Avoid installing applications from untrusted sources.

Fix this in P10 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8150 — 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-8150 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