The cycle collection (CC) implementation in Mozilla Firefox before 25.0, Firefox ESR 24.x before 24.1, Thunderbird before 24.1, and SeaMonkey before 2.22 does not properly determine the thread for release of an image object, which allows remote attackers to execute arbitrary code or cause a denial of service (race condition and application crash) via a large HTML document containing IMG elements, as demonstrated by the Never-Ending Reddit on reddit.com.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
| Link | Tags |
|---|---|
| https://bugzilla.mozilla.org/show_bug.cgi?id=910881 | |
| http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00005.html | vendor advisory |
| https://security.gentoo.org/glsa/201504-01 | vendor advisory |
| http://lists.opensuse.org/opensuse-security-announce/2013-11/msg00006.html | vendor advisory |
| https://oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A19066 | vdb entry signature |
| http://www.mozilla.org/security/announce/2013/mfsa2013-97.html | vendor advisory |