The MPEG4Extractor::parse3GPPMetaData function in MPEG4Extractor.cpp in libstagefright in Android before 5.1.1 LMY48I does not enforce a minimum size for UTF-16 strings containing a Byte Order Mark (BOM), which allows remote attackers to execute arbitrary code or cause a denial of service (integer underflow and memory corruption) via crafted 3GPP metadata, aka internal bug 20923261, a related issue to CVE-2015-3826.
CVE-2015-3828
This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 85.4% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.
- High exploitation likelihood — EPSS 85%
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v2.0 (legacy)
- 10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
- EG Score
- 10.0(low)
- EG Risk
- 84(Track)EG Risk 84/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 computedSeverity100% × 45%Exploitation85% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 85%
- EPSS %ILE
- 100%
- KEV
- Not listed
Published
October 1, 2015
Last Modified
May 6, 2026
References (12)
- security@androidhttp://www.huawei.com/en/psirt/security-advisories/hw-448928
- security@androidhttp://www.securityfocus.com/bid/76052
- security@androidhttp://www.securitytracker.com/id/1033094
- security@androidhttp://www1.huawei.com/en/security/psirt/security-bulletins/security-advisories/hw-448928.htm
- security@androidhttps://android.googlesource.com/platform/frameworks/av/+/f4f7e0c102819f039ebb1972b3dba1d3186bc1d1
- security@androidhttps://groups.google.com/forum/message/raw?msg=android-security-updates/Ugvu3fi6RQM/yzJvoTVrIQAJ
- af854a3a-2127-422b-91ae-364da2661108http://www.huawei.com/en/psirt/security-advisories/hw-448928
- af854a3a-2127-422b-91ae-364da2661108http://www.securityfocus.com/bid/76052
- af854a3a-2127-422b-91ae-364da2661108http://www.securitytracker.com/id/1033094
- af854a3a-2127-422b-91ae-364da2661108http://www1.huawei.com/en/security/psirt/security-bulletins/security-advisories/hw-448928.htm
- af854a3a-2127-422b-91ae-364da2661108https://android.googlesource.com/platform/frameworks/av/+/f4f7e0c102819f039ebb1972b3dba1d3186bc1d1
- af854a3a-2127-422b-91ae-364da2661108https://groups.google.com/forum/message/raw?msg=android-security-updates/Ugvu3fi6RQM/yzJvoTVrIQAJ
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 2× in last 7d / 4390× 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 4,445 total refreshes for this CVE.
- 2026-08-20 22:50 UTCEPSS rescore
- 2026-08-16 02:09 UTCEPSS rescore
- 2026-08-12 13:46 UTCEPSS rescore
- 2026-08-08 16:31 UTCEPSS rescore
- 2026-08-07 16:22 UTCEPSS rescore
- 2026-08-02 02:22 UTCEPSS rescore
- 2026-08-01 04:11 UTCEPSS rescore
- 2026-07-26 13:54 UTCEG score recompute▲ 10.00
- 2026-07-26 01:32 UTCGHSA enrichment
- 2026-07-26 01:31 UTCGHSA enrichment
- 2026-07-26 01:30 UTCGHSA enrichment
- 2026-07-26 01:29 UTCGHSA enrichment
- 2026-07-26 01:28 UTCGHSA enrichment
- 2026-07-26 01:27 UTCGHSA enrichment
- 2026-07-26 01:26 UTCGHSA enrichment
- 2026-07-26 01:25 UTCGHSA enrichment
- 2026-07-26 01:24 UTCGHSA enrichment
- 2026-07-26 01:23 UTCGHSA enrichment
- 2026-07-26 01:22 UTCGHSA enrichment
- 2026-07-26 01:21 UTCGHSA enrichment
- 2026-07-26 01:20 UTCGHSA enrichment
- 2026-07-26 01:19 UTCGHSA enrichment
- 2026-07-26 01:18 UTCGHSA enrichment
- 2026-07-26 01:17 UTCGHSA enrichment
- 2026-07-26 01:16 UTCGHSA enrichment
Show 75 moreShow fewer
- 2026-07-26 01:15 UTCGHSA enrichment
- 2026-07-26 01:14 UTCGHSA enrichment
- 2026-07-26 01:13 UTCGHSA enrichment
- 2026-07-26 01:12 UTCGHSA enrichment
- 2026-07-26 01:11 UTCGHSA enrichment
- 2026-07-26 01:10 UTCGHSA enrichment
- 2026-07-26 01:09 UTCGHSA enrichment
- 2026-07-26 01:08 UTCGHSA enrichment
- 2026-07-26 01:07 UTCGHSA enrichment
- 2026-07-26 01:06 UTCGHSA enrichment
- 2026-07-26 01:05 UTCGHSA enrichment
- 2026-07-26 01:04 UTCGHSA enrichment
- 2026-07-26 01:03 UTCGHSA enrichment
- 2026-07-26 01:02 UTCGHSA enrichment
- 2026-07-26 01:01 UTCGHSA enrichment
- 2026-07-26 01:00 UTCGHSA enrichment
- 2026-07-26 00:59 UTCGHSA enrichment
- 2026-07-26 00:58 UTCGHSA enrichment
- 2026-07-26 00:57 UTCGHSA enrichment
- 2026-07-26 00:56 UTCGHSA enrichment
- 2026-07-26 00:55 UTCGHSA enrichment
- 2026-07-26 00:54 UTCGHSA enrichment
- 2026-07-26 00:53 UTCGHSA enrichment
- 2026-07-26 00:52 UTCGHSA enrichment
- 2026-07-26 00:51 UTCGHSA enrichment
- 2026-07-26 00:50 UTCGHSA enrichment
- 2026-07-26 00:49 UTCGHSA enrichment
- 2026-07-26 00:48 UTCGHSA enrichment
- 2026-07-26 00:47 UTCGHSA enrichment
- 2026-07-26 00:46 UTCGHSA enrichment
- 2026-07-26 00:45 UTCGHSA enrichment
- 2026-07-26 00:44 UTCGHSA enrichment
- 2026-07-26 00:44 UTCGHSA enrichment
- 2026-07-26 00:43 UTCGHSA enrichment
- 2026-07-26 00:43 UTCGHSA enrichment
- 2026-07-26 00:42 UTCGHSA enrichment
- 2026-07-26 00:41 UTCGHSA enrichment
- 2026-07-26 00:41 UTCGHSA enrichment
- 2026-07-26 00:40 UTCGHSA enrichment
- 2026-07-26 00:39 UTCGHSA enrichment
- 2026-07-26 00:38 UTCGHSA enrichment
- 2026-07-26 00:37 UTCGHSA enrichment
- 2026-07-26 00:36 UTCGHSA enrichment
- 2026-07-26 00:36 UTCGHSA enrichment
- 2026-07-26 00:35 UTCGHSA enrichment
- 2026-07-26 00:34 UTCGHSA enrichment
- 2026-07-26 00:33 UTCGHSA enrichment
- 2026-07-26 00:33 UTCGHSA enrichment
- 2026-07-26 00:32 UTCGHSA enrichment
- 2026-07-26 00:32 UTCGHSA enrichment
- 2026-07-26 00:31 UTCGHSA enrichment
- 2026-07-26 00:30 UTCGHSA enrichment
- 2026-07-26 00:30 UTCGHSA enrichment
- 2026-07-26 00:29 UTCGHSA enrichment
- 2026-07-26 00:29 UTCGHSA enrichment
- 2026-07-26 00:28 UTCGHSA enrichment
- 2026-07-26 00:27 UTCGHSA enrichment
- 2026-07-26 00:26 UTCGHSA enrichment
- 2026-07-26 00:25 UTCGHSA enrichment
- 2026-07-26 00:24 UTCGHSA enrichment
- 2026-07-26 00:23 UTCGHSA enrichment
- 2026-07-26 00:22 UTCGHSA enrichment
- 2026-07-26 00:21 UTCGHSA enrichment
- 2026-07-26 00:21 UTCGHSA enrichment
- 2026-07-26 00:20 UTCGHSA enrichment
- 2026-07-26 00:20 UTCGHSA enrichment
- 2026-07-26 00:19 UTCGHSA enrichment
- 2026-07-26 00:18 UTCGHSA enrichment
- 2026-07-26 00:17 UTCGHSA enrichment
- 2026-07-26 00:16 UTCGHSA enrichment
- 2026-07-26 00:16 UTCGHSA enrichment
- 2026-07-26 00:15 UTCGHSA enrichment
- 2026-07-26 00:14 UTCGHSA enrichment
- 2026-07-26 00:13 UTCGHSA enrichment
- 2026-07-26 00:12 UTCGHSA enrichment
Frequently asked(4)
What is CVE-2015-3828?
When was CVE-2015-3828 disclosed?
Is CVE-2015-3828 actively exploited?
How do I remediate CVE-2015-3828?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2015-3828
Is Your Infrastructure Affected by CVE-2015-3828?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.