CVE-2017-8175
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 Bastet of some Huawei mobile phones with software earlier than Vicky-AL00AC00B167 versions, earlier than Victoria-AL00AC00B167 versions, earlier than Warsaw-AL00C00B191 versions has an insufficient input validation vulnerability due to the lack of parameter validation. An attacker may trick a user into installing a malicious APP. The APP can modify specific parameter to cause 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 · moderate confidenceA vulnerability in Huawei Bastet mobile phones allows a malicious application to modify a specific system parameter due to insufficient input validation, causing an arbitrary system reboot. The attacker must trick the user into installing the malicious app first.
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< vicky-al00ac00b167< victoria-al00ac00b167< warsaw-al00c00b191CVSS 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.
-
Identify your Huawei device modelGo to Settings > About Phone > Model Number (or similar path depending on Android version) to confirm the exact modelAffected if Model is NOT Vicky Al00a, Victoria Al00a, or Warsaw Al00 (these are the only affected models)
-
Check the installed software versionGo to Settings > About Phone > Version (or check for system updates) to find the build/version numberAffected if Version is Vicky-AL00AC00B167 or lower, Victoria-AL00AC00B167 or lower, or Warsaw-AL00C00B191 or lower (versions before the fixes)
-
Verify app installation source restrictionsGo to Settings > Security > Unknown Sources (or Settings > Apps > Special Access > Install Unknown Apps) to check if installation from untrusted sources is enabledAffected if Installation of apps from unknown sources is allowed (the attack requires user to install a malicious app first)
-
Review recently installed applicationsGo to Settings > Apps > Downloaded (or Apps & notifications) to list recently installed applications from unknown sourcesAffected if Any suspicious or untrusted third-party application is installed that was not obtained from a trusted source like the Google Play Store
You are affected if you have a Vicky Al00a, Victoria Al00a, or Warsaw Al00 device running a software version lower than B167 (for Vicky/Victoria) or B191 (for Warsaw), AND you have installed apps from untrusted sources.
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 Huawei Bastet devices to software version Vicky-AL00AC00B167 or later, Victoria-AL00AC00B167 or later, or Warsaw-AL00C00B191 or later. Only install applications from trusted sources to prevent initial compromise.
- Consultation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8175 — 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-8175 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