Bug 539242 – <www-client/seamonkey-2.32,www-client/seamonkey-bin-2.32: multiple vulnerabilities (CVE-2014-{8634,8635,8636,8637,8638,8639,8640,8641,8642})

• Product: Gentoo Security
• Status: RESOLVED FIXED

[Description Kristian Fiskerstrand (RETIRED) 2015-02-07 15:19:39 UTC]

+++ This bug was initially created as a clone of Bug #536564 +++ to track seamonkey bug

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

[Comment 1 Kristian Fiskerstrand (RETIRED) 2015-02-07 15:26:46 UTC]

Seamonkey-bin has not been bumped to unaffected version 2.32, but leasts start stabilization of the source package anyways. 

Arches, please stabilize

=www-client/seamonkey-2.32 
Stable targets: amd64 x86

This bug should not be closed before seamonkey-bin is either bumped && stabilized or p.masked.

[Comment 2 Agostino Sarubbo 2015-02-07 16:44:44 UTC]

amd64/x86 stable

[Comment 3 Agostino Sarubbo 2015-02-22 13:23:12 UTC]

CC'ing the maintainer.

[Comment 4 Aaron Bauman (RETIRED) 2016-07-01 06:11:32 UTC]

Added to existing GLSA.

[Comment 5 GLSAMaker/CVETool Bot 2017-01-03 13:02:11 UTC]

This issue was resolved and addressed in
 GLSA 201701-15 at https://security.gentoo.org/glsa/201701-15
by GLSA coordinator Thomas Deutschmann (whissi).

[Comment 6 Thomas Deutschmann (RETIRED) 2017-01-04 15:35:52 UTC]

SeaMonkey was removed from the GLSA.

[Comment 7 GLSAMaker/CVETool Bot 2017-01-13 15:00:44 UTC]

This issue was resolved and addressed in
 GLSA 201701-35 at https://security.gentoo.org/glsa/201701-35
by GLSA coordinator Aaron Bauman (b-man).