dbcve.org
AndroidOperating system · Google

CVE-2017-13310

HIGH · 7.8 CVSS v3.1 Published 2024-11-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 createFromParcel of ViewPager.java, there is a possible read/write serialization issue leading to a permissions bypass. This could lead to local escalation of privilege where an app can start an activity with system privileges with no additional execution privileges needed. User interaction is not needed for exploitation.

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

In createFromParcel of ViewPager.java, a serialization/deserialization issue exists where the ViewPager object is not properly validated when reconstructed from a Parcel. This allows a malicious app to manipulate parcel data during the read operation, bypassing permission checks and enabling an app to start activities with system-level privileges.

MitigationApply the AOSP patch for CVE-2017-13310 which adds proper validation and permission checks in the ViewPager createFromParcel method to ensure deserialized objects maintain correct security context.

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:= 6.0= 6.0.1= 7.0= 7.1.1= 7.1.2= 8.0= 8.1

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

CVSS:3.1/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 checks

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

  1. Check Android OS version
    Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell
    Affected if The version matches 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, or 8.1 exactly (not a later patch level)
  2. Verify ViewPager.java source for vulnerable createFromParcel
    Inspect AOSP framework source at frameworks/base/core/java/android/support/v4/view/ViewPager.java (or the equivalent location in the ROM). Look for the createFromParcel method and check if it performs proper Parcel validation before object reconstruction
    Affected if The createFromParcel method lacks proper validation or permission checks on the Parcel data being deserialized
  3. Check framework JAR for unpatched ViewPager class
    Decompile the framework JAR (framework.jar or android.jar) on the device/ROM. Locate the ViewPager class and examine the createFromParcel method implementation for missing validation logic
    Affected if The decompiled createFromParcel method shows no validation of Parcel contents before reconstructing the ViewPager object
  4. Identify apps using ViewPager with Parcelable IPC
    Review app manifests and code for components that use ViewPager and implement Parcelable interfaces for IPC communication. Check if any app sends ViewPager objects via Binder or other IPC mechanisms
    Affected if An app on the device uses ViewPager in a Parcelable context and receives data from external apps, enabling the parcel manipulation attack vector

A device is affected if it runs Android version 6.0 through 8.1 and the ViewPager createFromParcel method lacks proper Parcel validation, allowing a malicious app to manipulate deserialized data and escalate privileges.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the AOSP patch for CVE-2017-13310 which adds proper validation and permission checks in the ViewPager createFromParcel method to ensure deserialized objects maintain correct security context.

Recommended fix Moderate confidence

Android 8.0 (Oreo) or later, or apply the relevant 2017 Android Security Bulletin patch (refer to source.android.com security bulletins for the specific monthly update containing this fix)

  1. 1. Navigate to Settings > Security on the Android device
  2. 2. Check for and install the latest Android security patch update
  3. 3. Verify the device is running a security patch level that includes the fix for CVE-2017-13310
  4. 4. If available, update to Android 8.0 (Oreo) or later which contains the fix in createFromParcel of ViewPager.java
Caveat Upgrading to a newer Android version may introduce compatibility issues with older apps or change user interface behavior

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Android Scoped from the published advisory
  • Consultation12.0 h
  • Implementation24.0 h
  • Testing32.0 h
  • Review / QA16.0 h
84.0 hours of engineering $14,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-13310 — 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-13310 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