CVE-2017-8186
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 of earlier than MHA-AL00BC00B231 versions has a DOS 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 · high confidenceA denial of service vulnerability exists in Huawei mobile phones (Bastet component) running software versions earlier than MHA-AL00BC00B231. The lack of parameter validation allows a malicious application installed on the device to modify a specific system parameter, triggering an uncontrolled system reboot.
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< mha-al00bc00b231CVSS 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 device modelCheck if the Huawei mobile phone model is MHA-AL00a (or MHA Al00a). This can be found in the device Settings under 'About Phone' or by checking the original product packaging.Affected if The device model is Huawei MHA-AL00a or MHA Al00a
-
Check firmware versionNavigate to Settings > About Phone on the Huawei device and locate the 'Version' or 'Build number' field. Compare this version against the affected range: versions earlier than MHA-AL00BC00B231 are vulnerable.Affected if The installed firmware version is lower than MHA-AL00BC00B231 (for example, MHA-AL00BC00B230 or any earlier build)
-
Verify Bastet component presenceThe Bastet component is a Huawei internal system service. Check if it exists on the device by examining system apps or using a device diagnostic tool. This component handles system parameter management and is required for the vulnerability to be exploitable.Affected if The Bastet component is present and running on the device
-
Assess application installation riskThe vulnerability requires a malicious application to be installed on the device. Check if the device allows installation of apps from untrusted or unknown sources (Settings > Security > Unknown sources), or if the device has been jailbroken/rooted.Affected if The device permits installation of applications from untrusted sources or has been compromised with sideloaded apps
You are affected if your device is a Huawei MHA-AL00a model running firmware version earlier than MHA-AL00BC00B231, with the Bastet component present, and the device allows installation of potentially malicious applications.
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-supplied firmware update MHA-AL00BC00BC00B231 or later to affected Huawei mobile devices. Users should only install applications from trusted sources to reduce the risk of malicious app installation.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-8186 — 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-8186 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