CVE-2017-18069
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, improper message length calculation in oem_cmd_handler() while processing a WLAN_NL_MSG_OEM netlink message leads to buffer overread.
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 buffer overread vulnerability exists in the oem_cmd_handler() function within the WLAN driver of Android devices using Qualcomm MSM chipsets. The function improperly calculates message length when processing WLAN_NL_MSG_OEM netlink messages, allowing memory beyond buffer boundaries to be read. This could enable an attacker to leak sensitive kernel memory contents or potentially achieve 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 dataall versionsCVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 chipsetCheck /proc/cpuinfo or run 'getprop ro.hardware' or 'getprop ro.board.platform' to determine if the device uses a Qualcomm MSM chipsetAffected if The device does not use a Qualcomm MSM chipset - this vulnerability specifically affects Qualcomm MSM-based Android devices
-
Verify the WLAN driver module existsCheck for the presence of the WLAN driver module - look in /system/lib/modules/ or /kernel/drivers/net/wireless/ for Qualcomm WLAN driver files (typically named with 'wlan' or 'qcwlan' prefixes)Affected if No Qualcomm WLAN driver module is present on the device
-
Confirm the vulnerable function existsInspect the kernel or driver symbols for 'oem_cmd_handler' - use 'grep oem_cmd_handler /proc/kallsyms' or examine the WLAN driver module symbols if availableAffected if The oem_cmd_handler function is present in the WLAN driver, indicating the vulnerable code path exists
-
Check Android security patch levelRun 'getprop ro.build.version.security_patch' to obtain the installed security patch dateAffected if The security patch level is earlier than January 2018 - this CVE was publicly disclosed in the January 2018 Android Security Bulletin
A user is affected if they have an Android device with a Qualcomm MSM chipset, the oem_cmd_handler function is present in the WLAN driver, and the security patch level is before the January 2018 vendor update.
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 security patch from Qualcomm/Google for this CVE. Device manufacturers must release kernel updates addressing the improper length calculation in oem_cmd_handler(). Users should prioritize applying monthly security patches from their device vendors.
- Consultation12.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $24,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-18069 — 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-18069 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