LiveActive security incident?Get immediate response
CVE Record

CVE-2017-13318: In HeifDataSource::readAt of HeifDecoderImpl.cpp, there is a possible out of bounds read due to an integer...

In HeifDataSource::readAt of HeifDecoderImpl.cpp, there is a possible out of bounds read due to an integer overflow. 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

This CVE is an Android information disclosure issue in HEIF image handling. A crafted file could trigger an out-of-bounds read caused by integer overflow. Exploitation requires user interaction and no added privileges, so risk is meaningful but not emergency-level without evidence of active abuse.

Executive priority

Treat as a standard mobile patching priority, not a crisis. The business risk is confidentiality exposure from media handling, tempered by required user interaction and no evidence of active exploitation in the provided sources.

Technical view

HeifDataSource::readAt in HeifDecoderImpl.cpp can perform an out-of-bounds read due to integer overflow. The CVSS 3.1 score is 5.7, with high confidentiality impact, no integrity or availability impact, no privileges required, and user interaction required.

Likely exposure

Exposure is most relevant to Android or Pixel environments missing the vendor security update associated with the May 1, 2018 Pixel bulletin. The provided sources do not give precise affected release ranges beyond Google Android/Android Kernel wording.

Exploitation context

The sources indicate remote information disclosure requiring user interaction. CISA KEV status is false in the bundle, and no cited source states active exploitation or public exploit use.

Researcher notes

The record identifies CWE-125 and CWE-190 in Android HEIF decoding. Affected-version detail is limited, so validation should rely on vendor bulletin mapping and device patch levels rather than assumptions about unsupported release ranges.

Mitigation direction

  • Apply the relevant Google Android or Pixel security update from vendor guidance.
  • Verify devices meet or exceed the May 1, 2018 security patch guidance where applicable.
  • Prioritize managed devices that process untrusted media files.
  • Check OEM advisories if devices are not directly updated by Google.

Validation and detection

  • Inventory Android and Pixel devices and record security patch levels.
  • Confirm whether each device received the relevant May 2018 vendor security bulletin fixes.
  • Review MDM or EDR posture for unmanaged Android devices.
  • Track exceptions where OEM support or patch status is unclear.
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
cwe · low confidence lookup

CWE-190: 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-13318 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-13318Attack 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.