First published: Wed Mar 19 2014(Updated: )
The libxul.so!gfxContext::Polygon function in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and SeaMonkey before 2.25 allows remote attackers to obtain sensitive information from process memory, cause a denial of service (out-of-bounds read and application crash), or possibly bypass the Same Origin Policy via vectors involving MathML polygon rendering.
Credit: security@mozilla.org
Affected Software | Affected Version | How to fix |
---|---|---|
Mozilla Firefox | <28.0 | |
Mozilla Firefox ESR | >=24.0<24.4 | |
Mozilla SeaMonkey | <2.25 | |
Mozilla Thunderbird | <24.4 | |
redhat enterprise Linux desktop | =5.0 | |
redhat enterprise Linux desktop | =6.0 | |
redhat enterprise Linux eus | =6.5 | |
redhat enterprise Linux server | =5.0 | |
redhat enterprise Linux server | =6.0 | |
redhat enterprise Linux server aus | =6.5 | |
redhat enterprise Linux server eus | =6.5 | |
redhat enterprise Linux server tus | =6.5 | |
redhat enterprise Linux workstation | =5.0 | |
redhat enterprise Linux workstation | =6.0 | |
Debian GNU/Linux | =7.0 | |
Debian GNU/Linux | =8.0 | |
Ubuntu Linux | =12.04 | |
Ubuntu Linux | =12.10 | |
Ubuntu Linux | =13.10 | |
SUSE Linux Enterprise Software Development Kit | =11.0-sp3 | |
openSUSE | =11.4 | |
openSUSE | =12.3 | |
openSUSE | =13.1 | |
SUSE Linux Enterprise Desktop | =11-sp3 | |
SUSE Linux Enterprise Server | =11-sp3 | |
SUSE Linux Enterprise Server | =11-sp3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2014-1508 has a severity rating that suggests it can lead to a denial of service and information disclosure.
To fix CVE-2014-1508, users should update their Mozilla Firefox, Firefox ESR, Thunderbird, or SeaMonkey to the latest versions that address this vulnerability.
CVE-2014-1508 affects specific versions of Mozilla Firefox, Firefox ESR, Thunderbird, and SeaMonkey, along with several versions of Red Hat and Debian operating systems.
CVE-2014-1508 can allow attackers to conduct out-of-bounds reads, leading to application crashes and potential information leakage.
There are no known workarounds for CVE-2014-1508; the recommended action is to apply the security updates.