How severe is CVE-2015-3824?

No CVSS score has been assigned to CVE-2015-3824 yet. Review the advisory details and affected package list to assess your exposure.

Which products are affected by CVE-2015-3824?

CVE-2015-3824 affects the following products: google android.

How do I patch CVE-2015-3824?

No patch has shipped for CVE-2015-3824 yet — track the google android advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2015-3824 across my infrastructure?

Inventory every google android deployment and check each version against the affected-products list above.

How do I mitigate CVE-2015-3824 if there is no patch (or I can't update yet)?

Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Is CVE-2015-3824 actively exploited in the wild?

No public exploit code has been indexed for CVE-2015-3824 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2015-3824?

CVE-2015-3824 has an EPSS (Exploit Prediction Scoring System) score of 90.5%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

What type of vulnerability is CVE-2015-3824?

CVE-2015-3824 is classified as Buffer Overflow (CWE-119). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2015-3824?

CVE-2015-3824 affects google android. Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2015-3824 published, and has it been updated?

CVE-2015-3824 was published on October 1, 2015 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Not in CISA KEV

CVE-2015-3824 — Android

CVE-2015-3824 is a Buffer Overflow vulnerability in google android. EPSS puts its 30-day exploitation probability at 90.5% (100th percentile). No vendor fix is recorded yet; mitigation options are listed below.

The MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in Android before 5.1.1 LMY48I does not properly restrict size addition, which allows remote attackers…

Published

Oct 1, 2015

Updated

Jun 17, 2026

Affected

1 product

Patched

See advisory

Exploits

None indexed

Exploitation data as of Oct 28, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

90.5%probability of exploitation in next 30 days

Very High Risk0.00%

Lower risk than most CVEs100th percentile — riskier than 100% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Description

The MPEG4Extractor::parseChunk function in MPEG4Extractor.cpp in libstagefright in Android before 5.1.1 LMY48I does not properly restrict size addition, which allows remote attackers to execute arbitrary code or cause a denial of service (integer overflow and memory corruption) via a crafted MPEG-4 tx3g atom, aka internal bug 20923261.

Affected Products

1 product · 1 configurations

androidgoogle

≤ 5.1

range

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every google android deployment and check each version against the affected-products list above.
Remediation status
No patch has shipped for CVE-2015-3824 yet — track the google android advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Stop feeding it untrusted input: reject or quarantine files and payloads from unverified sources until you can upgrade, restrict accepted formats to the ones you actually need, and run the parsing or decoding step in a least-privileged sandbox or short-lived worker so a crash or corrupted read cannot reach the rest of the process. Alongside that, restrict the management interface to trusted networks and apply the vendor's recommended configuration mitigations.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2015-3824 being exploited in your environment?

Detect and block the exploit chain at execution, on systems you cannot patch yet.

Protect my workloads How runtime protection works