CVE-2015-0817

CVE-2015-0817 is a medium-severity vulnerability in Mozilla Firefox with a CVSS 2.0 base score of 6.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-17.

Key facts

Description

The asm.js implementation in Mozilla Firefox before 36.0.3, Firefox ESR 31.x before 31.5.2, and SeaMonkey before 2.33.1 does not properly determine the cases in which bounds checking may be safely skipped during JIT compilation and heap access, which allows remote attackers to read or write to unintended memory locations, and consequently execute arbitrary code, via crafted JavaScript.

Frequently asked questions

What is CVE-2015-0817?
The asm.js implementation in Mozilla Firefox before 36.0.3, Firefox ESR 31.x before 31.5.2, and SeaMonkey before 2.33.1 does not properly determine the cases in which bounds checking may be safely skipped during JIT compilation and heap access, which allows remote attackers to read or write to unintended memory locations, and consequently execute arbitrary code, via crafted JavaScript.
How severe is CVE-2015-0817?
CVE-2015-0817 has a CVSS 2.0 base score of 6.8, rated medium severity.
Is CVE-2015-0817 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 4% (88th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2015-0817?
CVE-2015-0817 primarily affects Mozilla Firefox. In total, 12 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2015-0817?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2015-0817 published?
CVE-2015-0817 was published on 2015-03-24 and last updated on 2026-06-17.

References

Affected products (12)

More vulnerabilities in Mozilla Firefox

All CVEs affecting Mozilla Firefox →

Other CWE-17 vulnerabilities

Browse all CWE-17 vulnerabilities →