LiveActive security incident?Get immediate response
CVE Record

CVE-2017-13310: In createFromParcel of ViewPager.java, there is a possible read/write serialization issue leading to a perm...

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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2017-13310 is an Android local privilege escalation issue. A malicious app on an affected device could start an activity with system privileges, bypassing intended permission controls. The source says no user interaction is needed, but the attacker needs local app-level access.

Executive priority

Prioritize this for legacy Android fleets. It is high impact if a malicious app runs on an affected device, but the available sources do not show internet-scale exploitation or KEV listing.

Technical view

The issue is in createFromParcel of ViewPager.java and is described as a read/write serialization problem causing a permissions bypass. CVSS 3.1 is 7.8: local attack vector, low complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to affected Android versions listed by the CVE: 6.0, 6.0.1, 7, 8, 8.1, and nyc-mr development branches. Managed fleets with old or unsupported Android builds are the main concern.

Exploitation context

The source bundle does not cite active exploitation, and KEV status is false. The described attacker position is a locally installed app with low privileges, not a remote unauthenticated network attacker.

Researcher notes

Evidence is limited to the CVE data and Android bulletin reference. Do not assume additional affected products or exploit availability. Focus validation on OS version, vendor patch mapping, and whether local app installation paths exist.

Mitigation direction

  • Review the Android May 2018 security bulletin and vendor guidance for applicable fixes.
  • Update affected devices to vendor builds that include the relevant Android security fixes.
  • Retire or isolate unsupported Android 6, 7, and 8 devices where updates are unavailable.
  • Restrict installation of untrusted apps, especially on legacy managed devices.
  • Use MDM policy to reduce sideloading and enforce device compliance.

Validation and detection

  • Inventory Android devices running versions listed as affected by the CVE.
  • Verify vendor security patch levels against the Android May 2018 bulletin.
  • Confirm unmanaged or unsupported devices are excluded from sensitive workflows.
  • Review MDM controls for sideloading, app trust, and compliance enforcement.
  • Document any affected devices that cannot receive vendor fixes.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-276: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-13310 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2017-13310Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
GoogleAndroid6.0., 6.0.1, 7, 8, 8.1, nyc-mr1-dev, nyc-mr2-devunaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-276 · source CWE mapping

Incorrect Default Permissions

Incorrect Default Permissions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.