dbcve.org
AndroidOperating system · Google

CVE-2017-13315

HIGH · 7.8 CVSS v3.1 Published 2024-11-19
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
80/100
Remediation priority · High
Zero-click Patch available

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 writeToParcel and createFromParcel of DcParamObject.java, there is a permission bypass due to a write size mismatch. This could lead to an elevation of privileges where the user 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

A detailed technical summary for this CVE is being prepared.

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

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
Patch available Apply the vendor patch
Vendor patch source.android.com →
Recommended fix High confidence

Android 8.0 (Oreo) or later with May 2018 security patch level; Android 7.1.2 with May 2018 patch if OEM supports it

  1. 1. Verify the current Android version on the affected device via Settings > About Phone > Android version
  2. 2. Check the device's patch level via Settings > About Phone > Android security patch level
  3. 3. If the device is running Android 6.0, 6.0.1, 7.0, or 7.1.1, it is vulnerable and no longer receiving official security patches
  4. 4. Contact the device manufacturer (OEM) to check if they have released a custom patch for this specific CVE
  5. 5. If no OEM patch is available, upgrade the device to a supported Android release (Android 8.0 Oreo or later) that includes the May 2018 security patch level
  6. 6. Alternatively, if the device supports it, install a custom ROM (such as LineageOS) that includes the Android May 2018 security updates
  7. 7. After upgrade, verify the patch level shows May 2018 or later via Settings > About Phone > Android security patch level
Caveat Devices running Android 6.0/6.0.1/7.0 may not receive official patches for this CVE from Google; upgrading to Android 8.0+ may require data backup as some devices may perform factory reset during major OS upgrades

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

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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