https://www.mozilla.org/it/security/advisories/mfsa2015-01 https://www.mozilla.org/it/security/advisories/mfsa2015-02 https://www.mozilla.org/it/security/advisories/mfsa2015-03 https://www.mozilla.org/it/security/advisories/mfsa2015-04 https://www.mozilla.org/it/security/advisories/mfsa2015-05 https://www.mozilla.org/it/security/advisories/mfsa2015-06 https://www.mozilla.org/it/security/advisories/mfsa2015-07 https://www.mozilla.org/it/security/advisories/mfsa2015-08 https://www.mozilla.org/it/security/advisories/mfsa2015-09
CVE-2014-8642 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8642): Mozilla Firefox before 35.0 and SeaMonkey before 2.32 do not consider the id-pkix-ocsp-nocheck extension in deciding whether to trust an OCSP responder, which makes it easier for remote attackers to obtain sensitive information by sniffing the network during a session in which there was an incorrect decision to accept a compromised and revoked certificate. CVE-2014-8641 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8641): Use-after-free vulnerability in the WebRTC implementation in Mozilla Firefox before 35.0, Firefox ESR 31.x before 31.4, and SeaMonkey before 2.32 allows remote attackers to execute arbitrary code via crafted track data. CVE-2014-8640 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8640): The mozilla::dom::AudioParamTimeline::AudioNodeInputValue function in the Web Audio API implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly restrict timeline operations, which allows remote attackers to cause a denial of service (uninitialized-memory read and application crash) via crafted API calls. CVE-2014-8639 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8639): Mozilla Firefox before 35.0, Firefox ESR 31.x before 31.4, Thunderbird before 31.4, and SeaMonkey before 2.32 do not properly interpret Set-Cookie headers within responses that have a 407 (aka Proxy Authentication Required) status code, which allows remote HTTP proxy servers to conduct session fixation attacks by providing a cookie name that corresponds to the session cookie of the origin server. CVE-2014-8638 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8638): The navigator.sendBeacon implementation in Mozilla Firefox before 35.0, Firefox ESR 31.x before 31.4, Thunderbird before 31.4, and SeaMonkey before 2.32 omits the CORS Origin header, which allows remote attackers to bypass intended CORS access-control checks and conduct cross-site request forgery (CSRF) attacks via a crafted web site. CVE-2014-8637 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8637): Mozilla Firefox before 35.0 and SeaMonkey before 2.32 do not properly initialize memory for BMP images, which allows remote attackers to obtain sensitive information from process memory via a crafted web page that triggers the rendering of malformed BMP data within a CANVAS element. CVE-2014-8636 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8636): The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with a DOM object that has a named getter, which might allow remote attackers to execute arbitrary JavaScript code with chrome privileges via unspecified vectors. CVE-2014-8635 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8635): Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors. CVE-2014-8634 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8634): Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 35.0, Firefox ESR 31.x before 31.4, Thunderbird before 31.4, and SeaMonkey before 2.32 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors.
What is the status here? I see firefox{,bin} and thunderbird{,bin} were bumped long time ago (not sure about seamonkey).
(In reply to Stephan Hartmann from comment #2) > What is the status here? I see firefox{,bin} and thunderbird{,bin} were > bumped long time ago (not sure about seamonkey). everything is in the tree, archs can be cc'd
Tracking seamonkey in bug 539242 Arches, please stabilize: =www-client/firefox-31.4.0 Stable targets: alpha amd64 arm hppa ia64 ppc pcc64 x86 =www-client/firefox-bin-31.4.0 Stable targets: amd64 x86 =mail-client/thunderbird-31.4.0 Stable targets: amd64 arm ppc ppc64 x86 =mail-client/thunderbird-bin-31.4.0 Stable targets: amd64 x86
amd64 stable
Stable for HPPA.
x86 stable
ppc64 stable
ppc stable
ia64 stable
Newer version begin stabilized in Bug #544056 Added to an existing GLSA Request.
This issue was resolved and addressed in GLSA 201504-01 at https://security.gentoo.org/glsa/201504-01 by GLSA coordinator Kristian Fiskerstrand (K_F).
