CVE-2017-17175
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 · uneditedShort Message Service (SMS) module of Mate 9 Pro Huawei smart phones with the versions before LON-AL00B 8.0.0.354(C00) has a Denial of Service (DoS) vulnerability. An unauthenticated attacker may set up a pseudo base station, and send special malware text message to the phone, causing the mobile phone to fail to make calls and send and receive text messages.
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 the SMS module of Huawei Mate 9 Pro smartphones running versions prior to LON-AL00B 8.0.0.354(C00). An attacker with a pseudo base station can send a specially crafted malware SMS message that crashes the SMS service, rendering the device unable to make calls or send/receive text messages.
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< lon-al00b_8.0.0.354\(c00\)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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:A/AC:L/PR:N/UI:N/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 Mate 9 ProNavigate to Settings > About Phone on the device and verify the model name displays as 'Mate 9 Pro' or the marketing code 'LON-AL00'Affected if Device model is not Huawei Mate 9 Pro - different models are not affected by this specific vulnerability
-
Identify the current firmware versionGo to Settings > About Phone > Version and record the build number displayed (such as LON-AL00B 8.0.0.XXX(C00) where XXX is a three-digit number)Affected if Unable to retrieve the firmware version from the device settings
-
Compare firmware version against the affected rangeCompare the recorded build number to 'LON-AL00B 8.0.0.354(C00)' - the version must be numerically less than 354 in the third octet to be within the vulnerable rangeAffected if Firmware version is LON-AL00B 8.0.0.354(C00) or higher (such as 355, 356, etc) - these versions include the patch
-
Verify SMS functionality is intact (optional confirmation)Attempt to send and receive a standard SMS message to confirm the SMS service is currently operationalAffected if SMS service is already crashed or unresponsive - this indicates the vulnerability has been exploited
The device is affected if it is a Huawei Mate 9 Pro running firmware version LON-AL00B 8.0.0.353(C00) or lower, as versions prior to LON-AL00B 8.0.0.354(C00) contain the vulnerable SMS module.
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 LON-AL00B 8.0.0.354(C00) or later to patch the SMS module vulnerability; until patched, users should be cautious of unexpected SMS messages from unknown sources.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17175 — 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-17175 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