← Back to results
Vulnerability record · public intelligence
CVE-2017-0542
UNKNOWN

CVE-2017-0542

Published Apr 7, 2017 · Updated Nov 3, 2026

Severity · CVSSUNKNOWN · Not scored
Known exploitationNot listed
EPSS / likelihood1.57%
QFinch risk scoreNot available

Original summary

Normalized public record · Updated Nov 3, 2026

A remote code execution vulnerability in libavc in Mediaserver could enable an attacker using a specially crafted file to cause memory corruption during media file and data processing. This issue is rated as Critical due to the possibility of remote code execution within the context of the Mediaserver process. Product: Android. Versions: 6.0, 6.0.1, 7.0, 7.1.1. Android ID: A-33934721.

Publisher and source text is retained separately from QFinch interpretation.

QFinch assessment

A remote code execution vulnerability in libavc in Mediaserver could enable an attacker using a specially crafted file to cause memory corruption during media file and data processing. This issue is rated as Critical due to the possibility of remote code execution within the context of the Mediaserver process. Product: Android. Versions: 6.0, 6.0.1, 7.0, 7.1.1. Android ID: A-33934721.

Evidence: public source records

Affected products

Affected scope reported by the available public evidence
Affected package, product or rangeFix status
Consult the referenced vendor advisory for affected versions.Consult source advisory

Matching a version is only one part of assessing exposure. QFinch has not assessed your environment on this public page.

Remediation

Apply the vendor-supported fixed release or mitigation, then verify the affected component is no longer reachable.

  1. Confirm the affected product and reachable code path exist in your environment.
  2. Apply the vendor-supported patch or mitigation from the primary advisory.
  3. Rescan the exact deployed revision and retain verification evidence.
Review primary references

Evidence coverage

FIRST-EPSSCVE-LIST-V5
SSVC priority
MEDIUM
Confidence
Not available
Aliases
None reported

Scores appear only when corresponding evidence exists. Missing data is never interpreted as zero risk.

Sources and record history

  1. source.android.com ↗
  2. android.googlesource.com ↗
  3. 97330 ↗
  4. 1038201 ↗

Record history

Published Apr 7, 2017 · Last refreshed Nov 3, 2026