CVE-2017-9714
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 · uneditedIn Android for MSM, Firefox OS for MSM, QRD Android, with all Android releases from CAF using the Linux kernel, an out of bound memory access may happen in limCheckRxRSNIeMatch in case incorrect RSNIE is received from the client in assoc request.
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 confidenceAn out-of-bounds memory access vulnerability exists in the limCheckRxRSNIeMatch function within the WiFi/LAN driver code of Android for MSM, Firefox OS for MSM, and QRD Android. The vulnerability is triggered when a malformed or incorrect RSN Information Element (RSNIE) is received from a client in an association request, potentially allowing denial of service or possibly code execution.
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= 8.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:L/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.
-
Confirm Android version is 8.0Check the device Android version in Settings > About Phone or run 'getprop ro.build.version.release'Affected if Version is exactly 8.0 (Android Oreo)
-
Verify WiFi driver component is presentCheck for the presence of WiFi/LAN driver modules in /system/lib/modules or /vendor/lib/modules, or inspect loaded kernel modules with 'lsmod'Affected if WiFi driver modules for MSM (Qualcomm) hardware are loaded and in use
-
Identify the specific WiFi firmware/driver versionCheck WiFi firmware version in /etc/firmware or /vendor/firmware, or check wlan driver version via 'wpa_cli status' or 'dmesg | grep wlan'Affected if The driver version matches the vulnerable MSM WiFi driver build for Android 8.0
-
Check if RSNIE processing is enabledVerify WiFi is configured to accept client associations with RSN (WPA2) security - this is typically enabled by default on any active WiFi Access PointAffected if WiFi AP or STA mode is active and processing RSNIE frames from clients or APs
A device is affected if it is running Android 8.0 with a Qualcomm MSM WiFi driver that includes the limCheckRxRSNIeMatch function and has WiFi capability enabled to process RSNIE frames.
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 CAF kernel patch for CVE-2017-9714 which adds proper bounds checking in the limCheckRxRSNIeMatch function to validate RSNIE length fields before memory access operations.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-9714 — 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-9714 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