CVE-2017-15322
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 of BGO-L03C158B003CUSTC158D001 and BGO-L03C331B009CUSTC331D001 have a DoS vulnerability due to insufficient input validation. An attacker could exploit this vulnerability by sending specially crafted NFC messages to the target device. Successful exploit could make a service crash.
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 Denial of Service vulnerability exists in specific Huawei smartphone firmware versions (BGO-L03C158B003CUSTC158D001 and BGO-L03C331B009CUSTC331D001) where insufficient input validation on NFC message processing allows an attacker within NFC range to send specially crafted messages that crash the NFC service.
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= bgo-l03c158b003custc158d001= bgo-l03c331b009custc331d001CVSS 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 modelCheck if the device is a Huawei Baggio L03a by going to Settings > About Phone > Model Number, or run: `getprop ro.product.model` via ADBAffected if Device model is NOT Huawei Baggio L03a (not affected)
-
Check firmware versionNavigate to Settings > About Phone > Build Number, or run: `getprop ro.build.version.emui` and `getprop ro.build.display.id` via ADBAffected if Firmware version is NOT bgo-l03c158b003custc158d001 AND NOT bgo-l03c331b009custc331d001 (not affected)
-
Verify NFC is enabledGo to Settings > Network & Internet > NFC (or Settings > Connections > NFC), or check via: `settings get secure nfc_enabled` via ADB shellAffected if NFC is disabled (the attack requires NFC to be on to receive the malicious message)
-
Check NFC service statusRun `dumpsys nfc` via ADB shell and check if the NFC service is actively runningAffected if NFC service is crashed or not running (may indicate the vulnerability has been triggered)
User is affected if they have a Huawei Baggio L03a running either bgo-l03c158b003custc158d001 or bgo-l03c331b009custc331d001 firmware with NFC enabled.
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 available; until then, disable NFC or exercise caution when receiving NFC messages from untrusted sources to reduce attack surface.
- 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-15322 — 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-15322 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