dbcve.org
AndroidOperating system · Google

CVE-2017-11001

MEDIUM · 5.5 CVSS v3.0 Published 2017-09-21
Fix available
A fix is available. Upgrade to after 8.0 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
In all Qualcomm products with Android releases from CAF using the Linux kernel, the length of the MAC address is not checked which may cause out of bounds read.

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 confidence

A missing bounds check on MAC address length in Qualcomm's Android Linux kernel allows an out-of-bounds read when processing MAC addresses. The code fails to validate the length parameter before using it to access memory, potentially exposing sensitive information or causing a denial of service.

MitigationApply the vendor patch from Qualcomm/CAF that adds proper MAC address length validation before memory access operations. Update affected devices to the patched Android release.

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
AndroidOperating system
Affected:<= 8.0

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Android OS version
    Run 'getprop ro.build.version.release' in a shell or check Settings > About Phone > Android version
    Affected if Version is 8.0 or lower (versions above 8.0 are not affected)
  2. Verify Qualcomm chipset or kernel
    Run 'getprop ro.hardware' or check kernel build info for Qualcomm identifiers
    Affected if Device uses a Qualcomm Snapdragon chipset and associated kernel (the vulnerability exists in Qualcomm-specific kernel code)
  3. Confirm network interface presence
    Run 'ip link show' or check /sys/class/net/ to list active network interfaces
    Affected if Device has any active network interfaces (WiFi, Ethernet, Bluetooth) that process MAC addresses - this is the code path where the vulnerability triggers

A device is affected if it runs Android 8.0 or lower on Qualcomm hardware and has any active network interface that processes MAC addresses, allowing the out-of-bounds read to occur during MAC address handling.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 8.0
Interim mitigation

Apply the vendor patch from Qualcomm/CAF that adds proper MAC address length validation before memory access operations. Update affected devices to the patched Android release.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-11001 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-11001 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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