CVE-2017-17201
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 · uneditedSome huawei smartphones with software BTV-DL09C233B350, Berlin-L21HNC432B360, Berlin-L22HNC636B360, Berlin-L24HNC567B360, Berlin-L21C10B130, Berlin-L21C185B132, Berlin-L21C464B130, Berlin-L22C346B140, Berlin-L22C636B160, Berlin-L23C605B131, Berlin-L23DOMC109B160, MHA-AL00AC00B125 have a DoS vulnerability. Due to insufficient input validation, an attacker could trick a user to execute a malicious application, which could be exploited by attacker to launch DoS attacks.
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 confidenceDenial of Service vulnerability in multiple Huawei smartphone models (BTV-DL09C233B350, Berlin-L21HNC432B360, Berlin-L22HNC636B360, and others) stemming from insufficient input validation. An attacker must trick a user into executing a malicious application, which can then be exploited to cause a DoS condition on the affected device.
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= btv-dl09c233b350= berlin-l21hnc432b360= berlin-l22hnc636b360= berlin-l24hnc567b360= berlin-l21c10b130= berlin-l21c185b132= berlin-l21c464b130= berlin-l22c346b140= berlin-l22c636b160= berlin-l23c605b131= berlin-l23domc109b160= mha-al00ac00b125CVSS 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 the device model number in Settings > About Phone or using 'getprop ro.product.model' via ADBAffected if Model is BTV-DL09, Berlin-L21, Berlin-L22, Berlin-L23, or MHA-AL00 (or variant)
-
Identify firmware versionCheck EMUI firmware version in Settings > About Phone > Version or using 'getprop ro.build.version.emui' via ADBAffected if Version matches any of: btv-dl09c233b350, berlin-l21hnc432b360, berlin-l22hnc636b360, berlin-l24hnc567b360, berlin-l21c10b130, berlin-l21c185b132, berlin-l21c464b130, berlin-l22c346b140, berlin-l22c636b160, berlin-l23c605b131, berlin-l23domc109b160, or mha-al00ac00b125
-
Verify third-party app installation capabilityCheck if 'Install unknown apps' or 'Allow from this source' settings are enabled for any untrusted app sources in Settings > Apps > Special accessAffected if Third-party application installation from unknown sources is permitted on the device
Device is affected if the model and firmware version match the affected list AND third-party app installation is enabled, allowing the required user interaction to trigger the DoS.
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-supplied firmware updates when released; advise users against installing applications from untrusted sources to reduce the attack surface for this user-interaction-dependent vulnerability.
- Consultation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,336.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17201 — 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-17201 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