LiveActive security incident?Get immediate response
CVE Record

CVE-2017-13276: In CProgramConfig_ReadHeightExt of tpdec_asc.cpp, there is a possible stack buffer overflow due to a missin...

In CProgramConfig_ReadHeightExt of tpdec_asc.cpp, there is a possible stack buffer overflow due to a missing bounds check. This could lead to a remote code execution with no additional execution privileges needed. User interaction is needed for exploitation. Product: Android. Versions: 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1. Android ID: A-70637599.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2017-13276 is an Android media parsing flaw that could allow remote code execution after user interaction. The issue is a missing bounds check leading to a possible stack buffer overflow. It affects Android 6.0 through 8.1. The provided sources do not report active exploitation.

Executive priority

Prioritize remediation for managed Android fleets with legacy devices. The business concern is potential code execution from user-triggered content handling, but urgency is reduced where devices are patched and no active exploitation is evidenced.

Technical view

The flaw is in CProgramConfig_ReadHeightExt in tpdec_asc.cpp. A missing bounds check can cause stack buffer overflow and potential remote code execution without additional privileges. Exploitation requires user interaction. The source bundle identifies Android 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, and 8.1 as affected.

Likely exposure

Exposure is mainly legacy Android devices running affected versions or devices without the April 2018 Android security bulletin fixes. Enterprise risk depends on remaining unmanaged or unsupported Android endpoints that can process attacker-supplied media or content requiring user interaction.

Exploitation context

The source states remote code execution is possible and user interaction is required. The bundle marks KEV as false, and no cited source confirms active exploitation. Treat exploit availability as unconfirmed based on the supplied evidence.

Researcher notes

Focus validation on patch level and affected Android branches rather than exploit reproduction. The public description identifies the vulnerable function and bug class but does not provide CVSS details, CWE mapping, exploit status, or device-specific patch nuances.

Mitigation direction

  • Apply Android security updates that include the April 2018 bulletin fixes.
  • Check device vendor guidance for model-specific patch availability.
  • Retire or isolate unsupported Android 6.0 through 8.1 devices.
  • Limit exposure to untrusted media or content on unpatched devices.

Validation and detection

  • Inventory Android devices and record OS version and security patch level.
  • Identify devices running Android 6.0 through 8.1 without April 2018 fixes.
  • Verify vendor bulletin coverage for each affected device model.
  • Confirm MDM compliance policies flag unsupported or unpatched devices.
Prepared
Confidence
high
Sources
3

Public sources used

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-13276 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
Google Inc.Android6.0, 6.0.1, 7.0, 7.1.1, 7.1.2, 8.0, 8.1Listed
Weakness

CWE details

No CWE listed

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