LiveActive security incident?Get immediate response
CVE Record

CVE-2017-13320: In impeg2d_bit_stream_flush() of libmpeg2dec there is a possible OOB read due to a missing bounds check.

In impeg2d_bit_stream_flush() of libmpeg2dec there is a possible OOB read due to a missing bounds check. This could lead to Remote DoS with no additional execution privileges needed. User interaction is needed for exploitation.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2017-13320 is an Android media-decoder flaw that can let a malicious media input crash affected devices or processes. The documented impact is denial of service, not data theft or code execution. Exploitation requires user interaction, which lowers urgency but still matters for fleets with older Android devices.

Executive priority

Treat this as a moderate mobile fleet hygiene issue. Prioritize remediation for unmanaged, customer-facing, or high-volume media-processing devices, but it does not indicate confirmed active exploitation or code execution from the provided evidence.

Technical view

The issue is a CWE-125 out-of-bounds read in impeg2d_bit_stream_flush() in libmpeg2dec, caused by a missing bounds check. The CVSS 3.1 score is 6.5: network-reachable, low complexity, no privileges required, user interaction required, and high availability impact only.

Likely exposure

Exposure is limited to Android versions 7, 7.1.1, 7.1.2, 8, and 8.1 as listed in the CVE bundle. Organizations are mainly exposed through legacy or unmanaged Android devices that still process untrusted media content.

Exploitation context

The source bundle does not show CISA KEV listing or other evidence of active exploitation. Public sources describe a remote denial-of-service condition requiring user interaction, but do not provide exploit-in-the-wild evidence.

Researcher notes

Evidence is limited to the CVE record, CVE List data, and Android Pixel bulletin reference. The bundle does not include a patch diff, proof of concept, crash details, or active exploitation reporting, so validation should focus on version and patch-state exposure.

Mitigation direction

  • Check Android and Pixel May 2018 security bulletin guidance for applicable updates.
  • Apply vendor security updates to affected Android 7.x and 8.x devices.
  • Retire or isolate unsupported devices that cannot receive relevant vendor fixes.
  • Limit exposure to untrusted media on legacy affected devices where practical.

Validation and detection

  • Inventory Android devices for versions 7, 7.1.1, 7.1.2, 8, and 8.1.
  • Verify affected devices received the applicable vendor security bulletin update.
  • Identify apps or workflows that process untrusted media on affected devices.
  • Confirm unsupported legacy devices are removed, isolated, or risk-accepted.
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-13320 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.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/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
GoogleAndroid7, 7.1.1, 7.1.2, 8, 8.1unaffected
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.