CVE-2017-0711
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 · uneditedA elevation of privilege vulnerability in the MediaTek networking driver. Product: Android. Versions: Android kernel. Android ID: A-36099953. References: M-ALPS03206781.
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 confidenceElevation of privilege vulnerability in the MediaTek networking driver within the Android kernel. This kernel-level vulnerability allows a local malicious application to potentially gain elevated privileges on affected devices using MediaTek chipsets.
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= 7.1.2CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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.
-
Check Android version is 7.1.2Go to Settings > About phone > Android version, or run 'adb shell getprop ro.build.version.release'Affected if Version shown is exactly 7.1.2 (this CVE affects only this specific version)
-
Verify device uses a MediaTek chipsetCheck device specifications in Settings > About phone > Hardware info, or run 'adb shell getprop ro.hardware' or use a system info app like CPU-ZAffected if Chipset is from MediaTek (MTK, MediaTek, or MTxxxx numbering)
-
Confirm MediaTek networking driver is presentRun 'adb shell ls /system/lib/modules/' to list kernel modules, then check for MediaTek networking driver files (typically named with 'wlan' or 'net' and 'mtk' prefixes)Affected if MediaTek wireless/network driver modules exist in /system/lib/modules/
-
Check kernel version for MediaTek driverRun 'adb shell uname -r' or 'adb shell cat /proc/version' to identify the kernel buildAffected if Kernel build is from Android 7.1.2 timeline and contains MediaTek driver components
Device is affected if it runs Android 7.1.2 exactly AND contains a MediaTek chipset with the vulnerable networking driver present and 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 Android security patch levels that include the MediaTek driver fix (2017-08 or later). Users of affected devices should ensure they receive and install OEM-provided system updates containing the MediaTek networking driver patch.
- Consultation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-0711 — 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-0711 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