First published: Tue Mar 24 2015(Updated: )
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.
Credit: security@mozilla.org security@mozilla.org
Affected Software | Affected Version | How to fix |
---|---|---|
Firefox | <=36.0.1 | |
Firefox | =31.0 | |
Firefox | =31.1.0 | |
Firefox | =31.1.1 | |
Firefox | =31.3.0 | |
Firefox | =31.5.1 | |
Firefox ESR | =31.1 | |
Firefox ESR | =31.2 | |
Firefox ESR | =31.3 | |
Firefox ESR | =31.4 | |
Firefox ESR | =31.5 | |
Mozilla SeaMonkey | <=2.33.0 | |
Firefox ESR | =31.0 | |
Firefox ESR | =31.1.0 | |
Firefox ESR | =31.1.1 | |
Firefox ESR | =31.3.0 | |
Firefox ESR | =31.5.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-0817 has a medium severity rating as it can lead to unauthorized memory access.
To mitigate CVE-2015-0817, users should update to the latest versions of Mozilla Firefox, Firefox ESR, or SeaMonkey.
CVE-2015-0817 affects Mozilla Firefox versions prior to 36.0.3, Firefox ESR versions before 31.5.2, and SeaMonkey versions before 2.33.1.
Yes, CVE-2015-0817 can be exploited by remote attackers to read or write memory without proper bounds checking.
Yes, CVE-2015-0817 has been addressed and patched in versions of Mozilla Firefox, Firefox ESR, and SeaMonkey released after the specified versions.