LiveActive security incident?Get immediate response
CVE Record

CVE-2017-13315: In writeToParcel and createFromParcel of DcParamObject.java, there is a permission bypass due to a write si...

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.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This Android flaw lets a local low-privileged actor bypass permissions and start an activity with system privileges. The source describes no need for user interaction. Business risk is mainly legacy or unpatched Android fleets, where compromise of a device could expose sensitive data and affect integrity or availability.

Executive priority

Treat this as a high-priority legacy Android patch and retirement issue, not an internet-wide emergency. Prioritize managed devices holding sensitive data or running unsupported Android versions.

Technical view

CVE-2017-13315 is a CWE-131 write size mismatch in DcParamObject.java writeToParcel and createFromParcel. The CVSS 3.1 score is 7.8, local attack vector, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely limited to Android 6, 6.0.1, 7, 8, 8.1, and listed nyc development builds that lack the relevant Android security update or OEM backport.

Exploitation context

The source bundle does not identify active exploitation, and KEV status is false. Exploitation is described as local, requiring low privileges and no user interaction. No exploit code or weaponized procedure is cited.

Researcher notes

Key evidence is limited to CVE metadata and the Android May 2018 bulletin reference. The record describes the vulnerable methods and privilege impact but does not provide device-specific OEM status, proof of exploitation, or detailed remediation beyond vendor updates.

Mitigation direction

  • Identify affected Android versions and listed development builds in managed inventory.
  • Apply OEM or Google updates corresponding to Android Security Bulletin 2018-05-01.
  • Retire or isolate devices that cannot receive the relevant Android security update.
  • Restrict untrusted app installation on legacy Android devices until updated.
  • Check vendor advisories for device-specific backports or support status.

Validation and detection

  • Inventory Android OS versions and security patch levels across managed devices.
  • Confirm devices show a patch level including the May 2018 Android bulletin fix.
  • Review MDM reports for unsupported Android 6, 7, 8, or 8.1 devices.
  • Verify high-risk devices cannot install apps from untrusted sources.
  • Track exceptions where OEM patch evidence is unavailable.
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-131: 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-13315 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-13315Attack 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, 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-131 · source CWE mapping

Incorrect Calculation of Buffer Size

Incorrect Calculation of Buffer Size represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.