From https://www.mozilla.org/security/announce/ : October 14, 2014 MFSA 2014-82 Accessing cross-origin objects via the Alarms API MFSA 2014-81 Inconsistent video sharing within iframe MFSA 2014-80 Key pinning bypasses MFSA 2014-79 Use-after-free interacting with text directionality MFSA 2014-78 Further uninitialized memory use during GIF MFSA 2014-77 Out-of-bounds write with WebM video MFSA 2014-76 Web Audio memory corruption issues with custom waveforms MFSA 2014-75 Buffer overflow during CSS manipulation MFSA 2014-74 Miscellaneous memory safety hazards (rv:33.0 / rv:31.2)
It should be noted that these new vulns don't seem to affect firefox and thunderbird 24.8.1; just all versions 25 (probably 30) and newer. Unsure if it's worth mentioning this in the summary though, as i think that would just make things overly complex; please make sure the GLSA doesn't mask the 24.x versions though. Ebuilds are in the tree. No stabilization requests yet, though, as I want to give firefox and thunderbird 31.2 a couple of weeks to flush out any regular bugs. As mentioned, 24.8.x are not affected and so their current stabilizations stand. (what should the whiteboard be set to, now?)
(In reply to Ian Stakenvicius from comment #1) > (what should the whiteboard be set to, now?) We need just to move from A2 to ~2
OK so I was wrong on 24.x not being vulnerable. It is still possibly safe, but upstream has dropped support for 24.x as of now and so vulnerability checks were not actually performed against those versions for these CVE's. I'll file stable bugs sooner rather than later for 31.2, and please mask 24.x in the GLSA.
*-bin packages are ready, still working on the 31.2.x source packages. amd64 and x86 arches please stabilize: www-client/firefox-bin-31.2.0-r1 mail-client/thunderbird-bin-31.2.0-r1 www-client/seamonkey-bin-33.0-r1
oops - that should be seamonkey-bin-2.30-r1 ; mozilla-33 is inside, sorry for the confusion. fixed below: (In reply to Ian Stakenvicius from comment #4) > *-bin packages are ready, still working on the 31.2.x source packages. > > amd64 and x86 arches please stabilize: > www-client/firefox-bin-31.2.0-r1 mail-client/thunderbird-bin-31.2.0-r1 www-client/seamonkey-bin-2.30-r1
amd64 stable
x86 stable. Maintainer(s), please cleanup. Security, please add it to the existing request, or file a new one.
no, we still need to stable www-client/firefox-31.2.0, mail-client/thunderbird-31.2.0, and add www-client/seamonkey-2.30. i set whiteboard to ebuild, but obviously feel free to start stable on firefox and thunderbird.
OK, i've gone through the bug lists, and I think we're as good to go as we're going to be on the source packages. Arches, please stabilize: www-client/firefox-31.2.0 Target KEYWORDS="alpha amd64 arm hppa ia64 ppc ppc64 x86" mail-client/thunderbird-31.2.0-r1 Target KEYWORDS="amd64 arm ppc ppc64 x86" Alpha team, if you do not wish to retain stable keywords on firefox please let me know. ia64 team, FYI, I've already done a successful test-build of firefox-31.2.0 on guppy.
dependency.bad 22 www-client/firefox/firefox-31.2.0.ebuild: DEPEND: amd64(default/linux/amd64/13.0) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: RDEPEND: amd64(default/linux/amd64/13.0) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: DEPEND: amd64(default/linux/amd64/13.0/desktop) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: RDEPEND: amd64(default/linux/amd64/13.0/desktop) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: DEPEND: amd64(default/linux/amd64/13.0/desktop/gnome) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: RDEPEND: amd64(default/linux/amd64/13.0/desktop/gnome) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: DEPEND: amd64(default/linux/amd64/13.0/desktop/gnome/systemd) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: RDEPEND: amd64(default/linux/amd64/13.0/desktop/gnome/systemd) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: DEPEND: amd64(default/linux/amd64/13.0/desktop/kde) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: RDEPEND: amd64(default/linux/amd64/13.0/desktop/kde) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: DEPEND: amd64(default/linux/amd64/13.0/desktop/kde/systemd) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: RDEPEND: amd64(default/linux/amd64/13.0/desktop/kde/systemd) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: DEPEND: amd64(default/linux/amd64/13.0/developer) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: RDEPEND: amd64(default/linux/amd64/13.0/developer) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: DEPEND: amd64(hardened/linux/amd64) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: RDEPEND: amd64(hardened/linux/amd64) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: DEPEND: amd64(hardened/linux/amd64/no-multilib) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: RDEPEND: amd64(hardened/linux/amd64/no-multilib) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: DEPEND: amd64(hardened/linux/amd64/no-multilib/selinux) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: RDEPEND: amd64(hardened/linux/amd64/no-multilib/selinux) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: DEPEND: amd64(hardened/linux/amd64/selinux) ['>=media-libs/mesa-10.2:*'] www-client/firefox/firefox-31.2.0.ebuild: RDEPEND: amd64(hardened/linux/amd64/selinux) ['>=media-libs/mesa-10.2:*'] Same for mail-client/thunderbird-31.2.0-r1.
@polynomial-c / mozilla: we stabilized seamonkey-bin but I don't see it in the advisories. Do we need to stabilize also seamonkey?
yeah >=media-libs/mesa-10.2 is unstable
*** Bug 528152 has been marked as a duplicate of this bug. ***
Most recent stable version =www-client/firefox-24.8.0 is vulnerable for a month now. Please mark >=media-libs/mesa-10.2 stable soon in order to bring www-client/firefox back in sync with www-client/firefox-bin which has already been stabilized on October 18th for the new ESR 31 branch. Thanks.
Also, www-client/seamonkey-2.30-r1 needs to be stabilized too. Also2, it's worth noting that there will be another round of vulnerability announcements and a new 31.x version in about a week.
nothing to do for the arches here.
(In reply to Christian Tietz from comment #14) > Most recent stable version =www-client/firefox-24.8.0 is vulnerable for a > month now. Please mark >=media-libs/mesa-10.2 stable soon in order to bring > www-client/firefox back in sync with www-client/firefox-bin which has > already been stabilized on October 18th for the new ESR 31 branch. Thanks. +1
Stabilise what now?
Stabilizations have been deprecated for all of these, in favour of the new bug 531408. Please stabilize 31.3.0 via that bug instead.
CVE-2014-{1574,1575,1576,1577,1578,1580,1581,1582,1583,1584,1585,1586}
Merging multiple bugs for www-client/firefox{,-bin}, mail-client/thunderbird{,-bin}, www-client/seamonkey{,-bin) under the latest bug 531408 which is undergoing stabilization with each bug either needing cleanup or some stabilization.
CVE-2014-1586 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1586): content/base/src/nsDocument.cpp in Mozilla Firefox before 33.0, Firefox ESR 31.x before 31.2, and Thunderbird 31.x before 31.2 does not consider whether WebRTC video sharing is occurring, which allows remote attackers to obtain sensitive information from the local camera in certain IFRAME situations by maintaining a session after the user temporarily navigates away. CVE-2014-1585 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1585): The WebRTC video-sharing feature in dom/media/MediaManager.cpp in Mozilla Firefox before 33.0, Firefox ESR 31.x before 31.2, and Thunderbird 31.x before 31.2 does not properly recognize Stop Sharing actions for videos in IFRAME elements, which allows remote attackers to obtain sensitive information from the local camera by maintaining a session after the user tries to discontinue streaming. CVE-2014-1584 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1584): The Public Key Pinning (PKP) implementation in Mozilla Firefox before 33.0 skips pinning checks upon an unspecified issuer-verification error, which makes it easier for remote attackers to bypass an intended pinning configuration and spoof a web site via a crafted certificate that leads to presentation of the Untrusted Connection dialog to the user. CVE-2014-1583 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1583): The Alarm API in Mozilla Firefox before 33.0 and Firefox ESR 31.x before 31.2 does not properly restrict toJSON calls, which allows remote attackers to bypass the Same Origin Policy via crafted API calls that access sensitive information within the JSON data of an alarm. CVE-2014-1582 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1582): The Public Key Pinning (PKP) implementation in Mozilla Firefox before 33.0 does not properly consider the connection-coalescing behavior of SPDY and HTTP/2 in the case of a shared IP address, which allows man-in-the-middle attackers to bypass an intended pinning configuration and spoof a web site by providing a valid certificate from an arbitrary recognized Certification Authority. CVE-2014-1581 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1581): Use-after-free vulnerability in DirectionalityUtils.cpp in Mozilla Firefox before 33.0, Firefox ESR 31.x before 31.2, and Thunderbird 31.x before 31.2 allows remote attackers to execute arbitrary code via text that is improperly handled during the interaction between directionality resolution and layout. CVE-2014-1580 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1580): Mozilla Firefox before 33.0 does not properly initialize memory for GIF images, which allows remote attackers to obtain sensitive information from process memory via a crafted web page that triggers a sequence of rendering operations for truncated GIF data within a CANVAS element. CVE-2014-1578 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1578): The get_tile function in Mozilla Firefox before 33.0, Firefox ESR 31.x before 31.2, and Thunderbird 31.x before 31.2 allows remote attackers to cause a denial of service (out-of-bounds write and application crash) or possibly execute arbitrary code via WebM frames with invalid tile sizes that are improperly handled in buffering operations during video playback. CVE-2014-1577 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1577): The mozilla::dom::OscillatorNodeEngine::ComputeCustom function in the Web Audio subsystem in Mozilla Firefox before 33.0, Firefox ESR 31.x before 31.2, and Thunderbird 31.x before 31.2 allows remote attackers to obtain sensitive information from process memory or cause a denial of service (out-of-bounds read, memory corruption, and application crash) via an invalid custom waveform that triggers a calculation of a negative frequency value. CVE-2014-1576 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1576): Heap-based buffer overflow in the nsTransformedTextRun function in Mozilla Firefox before 33.0, Firefox ESR 31.x before 31.2, and Thunderbird 31.x before 31.2 allows remote attackers to execute arbitrary code via Cascading Style Sheets (CSS) token sequences that trigger changes to capitalization style. CVE-2014-1575 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1575): Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 33.0 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via vectors related to improper interaction between threading and garbage collection in the GCRuntime::triggerGC function in js/src/jsgc.cpp, and unknown other vectors. CVE-2014-1574 (http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-1574): Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 33.0, Firefox ESR 31.x before 31.2, and Thunderbird 31.x before 31.2 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors.
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).
