LiveActive security incident?Get immediate response
CVE Record

CVE-2017-13308: In tscpu_write_GPIO_out and mtkts_Abts_write of mtk_ts_Abts.c, there is a possible buffer overflow in an ss...

In tscpu_write_GPIO_out and mtkts_Abts_write of mtk_ts_Abts.c, there is a possible buffer overflow in an sscanf due to improper input validation. This could lead to a local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.

MediumCVSS 6.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-13308 is an Android kernel issue involving improper input validation in MediaTek thermal driver code. A local attacker with high privileges could potentially trigger a buffer overflow and gain System-level execution. It is not a remote drive-by risk, but compromise impact is high on affected builds.

Executive priority

Treat as a moderate-priority endpoint hardening issue. It needs patch verification for affected Android fleets, especially unmanaged or legacy devices, but the available evidence does not support emergency response for active exploitation.

Technical view

The flaw is a CWE-120 buffer overflow in sscanf handling within tscpu_write_GPIO_out and mtkts_Abts_write in mtk_ts_Abts.c. CVSS 3.1 is 6.7: local attack vector, low complexity, high privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure appears limited to Android kernel builds containing the vulnerable mtk_ts_Abts.c code path. The source bundle names Google Android Kernel but does not enumerate exact device models, Android versions, or OEM downstream status.

Exploitation context

The CVE record indicates local escalation of privilege and no user interaction. KEV status is false, and the provided sources do not cite active exploitation or public exploit availability.

Researcher notes

Key gaps are affected-version precision and downstream OEM coverage. Validation should focus on kernel source lineage, patch level, and vendor bulletin mapping. Do not assume exposure for all Android devices without confirming the vulnerable driver code is present.

Mitigation direction

  • Review Google and OEM Android security bulletin guidance for CVE-2017-13308.
  • Apply applicable Android or vendor kernel security updates.
  • Prioritize devices using affected Android kernel builds or related MediaTek thermal driver code.
  • Restrict local privileged access on unmanaged or high-risk Android devices.
  • Retire devices no longer receiving vendor security updates.

Validation and detection

  • Inventory Android devices and kernel patch levels.
  • Check whether builds include the vulnerable mtk_ts_Abts.c code path.
  • Confirm June 2018 Pixel bulletin coverage where relevant.
  • Review OEM advisories for downstream patch status.
  • Document devices without vendor-confirmed remediation.
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-120: 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-13308 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
Medium
CVSS
6.7 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:H/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
6.7CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H0.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.7Medium
CVSS 3.1 vector shape for CVE-2017-13308Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:H/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
GoogleAndroidKernelunaffected
Weakness

CWE details

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

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.