CVE-2017-17224
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 smart phones with versions earlier than Harry-AL00C 9.1.0.206(C00E205R3P1) have a null pointer dereference vulnerability. An attacker crafts specific packets and sends to the affected product to exploit this vulnerability. Successful exploitation may cause the affected phone abnormal.
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 confidenceThis is a null pointer dereference vulnerability in Huawei smartphones running versions earlier than Harry-AL00C 9.1.0.206(C00E205R3P1). An attacker exploits this by sending specially crafted network packets to the targeted phone, which triggers the null pointer dereference and causes the device to become abnormal (likely crash or freeze).
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< harry-al00c_9.1.0.206\(c00e205r3p1\)< v100r001c02b023CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck if the device is a Huawei Hg655m router or Huawei smartphone in the Harry-AL00 series. For phones, go to Settings > About Phone > Model Number. For routers, check the device label or web interface.Affected if The device is a Huawei Hg655m or Huawei smartphone in the Harry-AL00 series.
-
Determine the installed firmware versionFor Huawei smartphones: Settings > About Phone > Version. For Hg655m router: log into the web management interface and check the firmware version under System or Status.Affected if The exact version string is visible.
-
Compare version against affected rangeFor smartphones, compare the version to Harry-AL00C 9.1.0.206(C00E205R3P1). For Hg655m, compare to v100r001c02b023. If your version number is lower than these thresholds, you are in the affected range.Affected if Installed version is earlier than Harry-AL00C 9.1.0.206(C00E205R3P1) for smartphones, or earlier than v100r001c02b023 for Hg655m routers.
-
Verify network accessibility of the deviceDetermine if the device is exposed to untrusted networks. For phones, check if mobile data or Wi-Fi is enabled in untrusted locations. For routers, check if management interfaces are accessible from the WAN side.Affected if The device is reachable from untrusted network sources.
If the device is a Huawei Hg655m or Harry-AL00 series smartphone with firmware earlier than the specified version thresholds and is accessible from untrusted networks, the environment is affected by this CVE.
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 affected Huawei devices to version Harry-AL00C 9.1.0.206(C00E205R3P1) or later. As a defense-in-depth measure, restrict exposure to untrusted network sources.
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17224 — 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-17224 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