CVE-2016-2417

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-17. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Exploit-DB (verified), public exploit)
CISA-KEV: Not listedEPSS PROB: 5%CVSS: 9.8Exploit: Exploit-DB (verified) · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

media/libmedia/IOMX.cpp in mediaserver in Android 4.x before 4.4.4, 5.0.x before 5.0.2, 5.1.x before 5.1.1, and 6.x before 2016-04-01 does not initialize a parameter data structure, which allows attackers to obtain sensitive information from process memory, and consequently bypass an unspecified protection mechanism, via unspecified vectors, as demonstrated by obtaining Signature or SignatureOrSystem access, aka internal bug 26914474.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Track*)
EG Risk 75/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
5%
EPSS %ILE
92%
KEV
Not listed

Published

April 18, 2016

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Jul 27, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

Google Android - IOMX 'getConfig'/'getParameter' Information Disclosure - Android dos Exploit

https://www.exploit-db.com/exploits/39685/
generic

1171e7c047bf79e7c93342bb6a812c9edd86aa84 - platform/frameworks/av - Git at Google

https://android.googlesource.com/platform/frameworks/av/+/1171e7c047bf79e7c93342bb6a812c9edd86aa84
generic

Nexus Security Bulletin—April 2016  |  Android Open Source Project

http://source.android.com/security/bulletin/2016-04-02.html

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 104 total refreshes for this CVE.

  1. 2026-07-26 14:50 UTCEPSS rescore
  2. 2026-07-25 14:13 UTCEPSS rescore
  3. 2026-07-23 14:14 UTCEPSS rescore
  4. 2026-07-23 01:22 UTCEG score recompute
  5. 2026-07-22 22:01 UTCEG score recompute
  6. 2026-07-22 14:04 UTCEPSS rescore
  7. 2026-07-21 15:21 UTCEPSS rescore
  8. 2026-07-21 15:21 UTCEPSS rescore
  9. 2026-07-20 17:03 UTCEPSS rescore
  10. 2026-07-19 14:27 UTCEPSS rescore
  11. 2026-07-19 02:26 UTCEPSS rescore
  12. 2026-07-19 02:26 UTCEPSS rescore
  13. 2026-07-18 10:00 UTCEPSS rescore
  14. 2026-07-18 10:00 UTCEPSS rescore
  15. 2026-07-16 16:59 UTCEPSS rescore
  16. 2026-07-16 16:59 UTCEPSS rescore
  17. 2026-07-15 16:54 UTCEPSS rescore
  18. 2026-07-15 16:54 UTCEPSS rescore
  19. 2026-07-15 01:56 UTCEPSS rescore
  20. 2026-07-15 01:56 UTCEPSS rescore
  21. 2026-07-13 22:26 UTCEPSS rescore
  22. 2026-07-13 06:09 UTCEPSS rescore
  23. 2026-07-12 05:43 UTCEPSS rescore
  24. 2026-07-12 05:43 UTCEPSS rescore
  25. 2026-07-11 08:23 UTCEPSS rescore
Show 75 more
  1. 2026-07-09 19:05 UTCEPSS rescore
  2. 2026-07-08 15:10 UTCEPSS rescore
  3. 2026-07-07 13:42 UTCEPSS rescore
  4. 2026-07-06 16:24 UTCEPSS rescore
  5. 2026-07-06 16:24 UTCEPSS rescore
  6. 2026-07-06 02:20 UTCEPSS rescore
  7. 2026-07-06 02:20 UTCEPSS rescore
  8. 2026-07-05 02:27 UTCEPSS rescore
  9. 2026-07-04 06:28 UTCEPSS rescore
  10. 2026-07-01 15:02 UTCEPSS rescore
  11. 2026-06-30 23:19 UTCEPSS rescore
  12. 2026-06-28 14:04 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-27 03:05 UTCEPSS rescore
  15. 2026-06-27 03:05 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-25 13:47 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-22 14:23 UTCEPSS rescore
  22. 2026-06-21 01:57 UTCEPSS rescore
  23. 2026-06-21 01:57 UTCEPSS rescore
  24. 2026-06-19 19:23 UTCEPSS rescore
  25. 2026-06-19 19:23 UTCEPSS rescore
  26. 2026-06-18 17:50 UTCEPSS rescore
  27. 2026-06-17 17:50 UTCEPSS rescore
  28. 2026-06-17 17:50 UTCEPSS rescore
  29. 2026-06-16 17:50 UTCEPSS rescore
  30. 2026-06-16 17:50 UTCEPSS rescore
  31. 2026-06-15 17:45 UTCEPSS rescore
  32. 2026-06-14 23:14 UTCEPSS rescore
  33. 2026-06-13 22:57 UTCEPSS rescore
  34. 2026-06-13 22:57 UTCEPSS rescore
  35. 2026-06-12 23:09 UTCEPSS rescore
  36. 2026-06-12 23:09 UTCEPSS rescore
  37. 2026-06-11 13:57 UTCEPSS rescore
  38. 2026-06-10 22:15 UTCEPSS rescore
  39. 2026-06-10 13:18 UTCEPSS rescore
  40. 2026-06-08 14:14 UTCEPSS rescore
  41. 2026-06-07 15:22 UTCEPSS rescore
  42. 2026-06-07 15:22 UTCEPSS rescore
  43. 2026-06-06 13:45 UTCEPSS rescore
  44. 2026-06-05 22:44 UTCEPSS rescore
  45. 2026-06-04 13:10 UTCEPSS rescore
  46. 2026-06-04 13:10 UTCEPSS rescore
  47. 2026-06-02 20:10 UTCEPSS rescore
  48. 2026-06-01 13:49 UTCEPSS rescore
  49. 2026-06-01 13:49 UTCEPSS rescore
  50. 2026-05-31 22:28 UTCEPSS rescore
  51. 2026-05-31 22:28 UTCEPSS rescore
  52. 2026-05-31 00:14 UTCEPSS rescore
  53. 2026-05-29 13:41 UTCEPSS rescore
  54. 2026-05-28 13:42 UTCEPSS rescore
  55. 2026-05-28 13:42 UTCEPSS rescore
  56. 2026-05-27 13:38 UTCEPSS rescore
  57. 2026-05-27 13:38 UTCEPSS rescore
  58. 2026-05-26 13:42 UTCEPSS rescore
  59. 2026-05-26 07:16 UTCEPSS rescore
  60. 2026-05-24 16:43 UTCEPSS rescore
  61. 2026-05-21 22:40 UTCEPSS rescore
  62. 2026-05-20 22:37 UTCEPSS rescore
  63. 2026-05-20 22:37 UTCEPSS rescore
  64. 2026-05-20 22:37 UTCEPSS rescore
  65. 2026-05-20 11:21 UTCEPSS rescore
  66. 2026-05-20 11:21 UTCEPSS rescore
  67. 2026-05-20 11:21 UTCEPSS rescore
  68. 2026-05-20 08:48 UTCGHSA enrichment
  69. 2026-05-20 04:54 UTCGHSA enrichment
  70. 2026-05-20 00:52 UTCGHSA enrichment
  71. 2026-05-19 20:51 UTCGHSA enrichment
  72. 2026-05-19 16:57 UTCGHSA enrichment
  73. 2026-05-19 12:46 UTCGHSA enrichment
  74. 2026-05-19 08:43 UTCGHSA enrichment
  75. 2026-05-19 04:49 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-39685✓ verified
    First seen Apr 11, 2016

    Google Android - IOMX 'getConfig'/'getParameter' Information Disclosure

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2016-2417?
CVE-2016-2417 is a critical vulnerability published on April 18, 2016. media/libmedia/IOMX.cpp in mediaserver in Android 4.x before 4.4.4, 5.0.x before 5.0.2, 5.1.x before 5.1.1, and 6.x before 2016-04-01 does not initialize a parameter data structure, which allows attackers to obtain sensitive information from process memory, and consequently bypass an unspecified…
When was CVE-2016-2417 disclosed?
CVE-2016-2417 was first published in the National Vulnerability Database on April 18, 2016, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2016-2417 actively exploited?
CVE-2016-2417 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 5% probability of exploitation in the next 30 days, which ranks it in the top 8.3% of all scored CVEs.
What is the CVSS score of CVE-2016-2417?
CVE-2016-2417 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2016-2417?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2016-2417, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-2417

Explore →

Is Your Infrastructure Affected by CVE-2016-2417?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs