CVE-2016-2419

media/libmedia/IDrm.cpp in mediaserver in Android 6.x before 2016-04-01 does not initialize a certain key-request 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 26323455.

Published: 2016-04-17 Last update: 2026-06-16 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2016-2419 is rated Moderate Risk (57.9/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 0.80%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2016-2419

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.20% 0.80% +0.60%
2 2025-07-13 0.08% 0.20% +0.12%
3 2025-03-30 — 0.08% —

Full EPSS history (6 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2016-2419

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.0 CRITICAL
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
10.0 2.0 HIGH
AV:N/AC:L/Au:N/C:C/I:C/A:C Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
 10.0 10.0 [email protected]

Weakness enumeration for CVE-2016-2419

OS Trackers for CVE-2016-2419

vendor priority summary link
ubuntu medium CVE-2016-2419 medium priority: Ubuntu including 1 source packages (android), 9 status rows across 9 suites (artful, bionic, precise, trusty, upstream, wily, xenial, yakkety, zesty): DNE 4, ignored 4, released 1. https://ubuntu.com/security/CVE-2016-2419

Affected software / configurations for CVE-2016-2419

Vendor Product Version Raw CPE
google android 6.0 cpe:2.3:o:google:android:6.0:*:*:*:*:*:*:*
google android 6.0.1 cpe:2.3:o:google:android:6.0.1:*:*:*:*:*:*:*

References for CVE-2016-2419

cvelogic Threat Intelligence