How severe is CVE-2015-1538?

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

Which packages are affected by CVE-2015-1538?

Affected package information for CVE-2015-1538 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2015-1538?

No fixed version has been published for CVE-2015-1538 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

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

Yes. There are 6 known exploit references for CVE-2015-1538, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

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

CVE-2015-1538 has an EPSS (Exploit Prediction Scoring System) score of 99.1%, 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-1538?

CVE-2015-1538 is classified as CWE-189 (CWE-189). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

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

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

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

CVE-2015-1538

Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android before 5.1.1 LMY48I allows remote attackers to execute arbitrary…

Published

Oct 1, 2015

Updated

May 6, 2026

Affected

0 pkgs

Patched

None yet

Exploits

6 known

EPSS Exploitation Probability

via FIRST.org ↗

99.1%probability of exploitation in next 30 days

Very High Risk100th percentile+11.86%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

Integer overflow in the SampleTable::setSampleToChunkParams function in SampleTable.cpp in libstagefright in Android before 5.1.1 LMY48I allows remote attackers to execute arbitrary code via crafted atoms in MP4 data that trigger an unchecked multiplication, aka internal bug 20139950, a related issue to CVE-2015-4496.

Affected Products

1 product · 1 configurations

androidgoogle

≤ 5.1

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-38124remoteandroid✓ Verified

Google Android - 'Stagefright' Remote Code Execution

by Joshua J. Drake · Sep 9, 2015

Exploit-DB Source

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2015-1538 in your stack?

O3 detects CVE-2015-1538 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works