VDB

CVE-2017-0503

CVE-2017-0503 PUBLISHED

Reported by google_android · Published March 8, 2017

An elevation of privilege vulnerability in MediaTek components, including the M4U driver, sound driver, touchscreen driver, GPU driver, and Command Queue driver, could enable a local malicious application to execute arbitrary code within the context of the kernel. This issue is rated as Critical due to the possibility of a local permanent device compromise, which may require reflashing the operating system to repair the device. Product: Android. Versions: N/A. Android ID: A-28449045. References: M-ALPS02710075.

Affected products

VendorProductVersions
Google Inc.Androidn/a
Google Inc.Android*

Timeline

  • Mar 7, 2017 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Oct 24, 2025 CVE Updated
  • Jun 1, 2026 Security Advisory
  • Oct 5, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2017-0503
vulnetix vdb fixes CVE-2017-0503

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-0503/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

  • x_refsource_CONFIRM
  • 1037968 vdb-entryx_refsource_SECTRACK
  • 96726 vdb-entryx_refsource_BID
Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›