CVE-2017-13247
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 the Pixel 2 bootloader, there is a missing permission check which bypasses carrier bootloader lock. This could lead to local elevation of privileges with user execution privileges needed. User interaction is not needed for exploitation. Product: Android. Versions: Android kernel. Android ID: A-71486645.
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 missing permission check in the Pixel 2 bootloader allows bypassing carrier bootloader lock mechanisms, enabling local privilege elevation. The vulnerability exists in the bootloader component and requires user execution privileges but no user interaction for exploitation.
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
- 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 device model is Pixel 2Check the device model number in Settings > About Phone > Model Number, or run `getprop ro.product.model` via ADBAffected if The device model is not Pixel 2 (the vulnerability only affects Pixel 2 bootloader)
-
Check bootloader versionBoot the device into fastboot mode and run `fastboot getvar version` or use `getprop ro.bootloader` via ADBAffected if Unable to retrieve bootloader version or version is unpatched (all versions of Pixel 2 bootloader prior to security update are potentially affected)
-
Verify bootloader lock statusBoot into fastboot mode and run `fastboot oem device-info` to check if the bootloader is locked or unlockedAffected if Bootloader is unlocked, or device shows as vulnerable to lock bypass (the flaw allows bypassing carrier lock mechanisms)
-
Check Android security patch levelGo to Settings > About Phone > Android version > Security patch level, or run `getprop ro.build.version.security_patch` via ADBAffected if Security patch level is earlier than the January 2018 Android Security Update that addressed this CVE (CVE-2017-13247)
The device is affected if it is a Pixel 2 with a bootloader version prior to the January 2018 security update, regardless of lock status, since the vulnerability allows bypassing the lock mechanism itself.
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 available Android security updates/patches for Pixel 2 devices. Since this is a bootloader-level vulnerability, flashing updated firmware from Google's official sources is required. Device users should ensure they are running the latest carrier-approved software version.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-13247 — 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-13247 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