LiveActive security incident?Get immediate response
CVE Record

CVE-2017-13317: In HeifDecoderImpl::getScanline of HeifDecoderImpl.cpp, there is a possible out of bounds read due to impro...

In HeifDecoderImpl::getScanline of HeifDecoderImpl.cpp, there is a possible out of bounds read due to improper input validation. This could lead to remote information disclosure with no additional execution privileges needed. User interaction is needed for exploitation.

MediumCVSS 5.7Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-13317 is an Android issue where improper validation in HEIF image decoding may let an attacker read information from memory. It requires user interaction and does not grant code execution. Business urgency is moderate for organizations with Android or Pixel devices that may not include the May 2018 vendor security fixes.

Executive priority

Treat as a moderate mobile confidentiality risk. Prioritize remediation for fleets with unmanaged, legacy, or unsupported Android devices, especially where users may open external media. It is not currently evidenced as actively exploited in the provided sources.

Technical view

The source describes a CWE-125 out-of-bounds read in HeifDecoderImpl::getScanline in HeifDecoderImpl.cpp. CVSS 3.1 is 5.7 with adjacent attack vector, low complexity, no privileges, user interaction required, high confidentiality impact, and no integrity or availability impact. Exact affected Android versions are not detailed in the provided bundle.

Likely exposure

Exposure is most relevant to Android or Pixel devices missing the referenced Google May 2018 security bulletin fixes. The bundle lists Google Android and an Android Kernel version label, but does not provide exact device models, OS releases, or patch-level mapping.

Exploitation context

The bundle does not cite active exploitation, and KEV status is false. Exploitation requires user interaction and appears limited to information disclosure through an out-of-bounds read, not arbitrary code execution.

Researcher notes

Evidence is sparse. The record identifies the vulnerable function, weakness class, impact, CVSS vector, and a Google Pixel bulletin reference, but not exact affected release ranges or detailed remediation text. Avoid assuming broader Android exposure beyond the cited vendor context.

Mitigation direction

  • Apply Google Android or Pixel security updates referenced in the May 2018 bulletin.
  • Confirm unsupported Android devices have vendor guidance or replacement plans.
  • Restrict processing of untrusted HEIF media where patching is delayed.
  • Track CVE-2017-13317 in mobile vulnerability management workflows.

Validation and detection

  • Inventory Android and Pixel devices in scope.
  • Verify devices include the referenced May 2018 security bulletin fixes or later vendor updates.
  • Check mobile device management records for stale Android patch levels.
  • Review exception lists for unsupported devices still handling external media.
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-125: 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-13317 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
5.7 (3.1)
Known Exploited
No
Published

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

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
5.7CVSS 3.1MediumCVSS:3.1/AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N2.13.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

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

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
GoogleAndroidAndroid Kernelunaffected
Weakness

CWE details

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

CWE-125 · source CWE mapping

Out-of-bounds Read

Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.