Get Gentoo!
gentoo.org sites
gentoo.org Wiki Bugs Forums Packages
Planet Archives Sources
Infra Status
summaryrefslogtreecommitdiff
path: root/glsa-201701-15.xml
diff options
context:
space:
mode:
authorThomas Deutschmann <whissi@gentoo.org>2017-01-03 13:59:25 +0100
committerThomas Deutschmann <whissi@gentoo.org>2017-01-03 13:59:25 +0100
commit695dcf4c981de23e1a3c6e4e0fc376a7d5281a98 (patch)
treef4b3aa0ad279d4286afe4b5fb80abce50246031d /glsa-201701-15.xml
parentAdd bug 603420 to GLSA 201612-56 (diff)
downloadglsa-695dcf4c981de23e1a3c6e4e0fc376a7d5281a98.tar.gz
glsa-695dcf4c981de23e1a3c6e4e0fc376a7d5281a98.tar.bz2
glsa-695dcf4c981de23e1a3c6e4e0fc376a7d5281a98.zip
Add GLSA 201701-15
Diffstat (limited to 'glsa-201701-15.xml')
-rw-r--r--glsa-201701-15.xml222
1 files changed, 222 insertions, 0 deletions
diff --git a/glsa-201701-15.xml b/glsa-201701-15.xml
new file mode 100644
index 00000000..893c2fe8
--- /dev/null
+++ b/glsa-201701-15.xml
@@ -0,0 +1,222 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
+<glsa id="201701-15">
+ <title>Mozilla Firefox, SeaMonkey, Thunderbird: Multiple vulnerabilities</title>
+ <synopsis>Multiple vulnerabilities have been found in Mozilla Firefox,
+ SeaMonkey, and Thunderbird the worst of which could lead to the execution
+ of arbitrary code.
+ </synopsis>
+ <product type="ebuild">firefox, thunderbird, seamonkey</product>
+ <announced>January 03, 2017</announced>
+ <revised>January 03, 2017: 1</revised>
+ <bug>539242</bug>
+ <bug>541506</bug>
+ <bug>581326</bug>
+ <bug>590330</bug>
+ <bug>594616</bug>
+ <bug>599924</bug>
+ <bug>601320</bug>
+ <bug>602576</bug>
+ <bug>604024</bug>
+ <access>remote</access>
+ <affected>
+ <package name="www-client/firefox" auto="yes" arch="*">
+ <unaffected range="ge">45.6.0</unaffected>
+ <vulnerable range="lt">45.6.0</vulnerable>
+ </package>
+ <package name="www-client/firefox-bin" auto="yes" arch="*">
+ <unaffected range="ge">45.6.0</unaffected>
+ <vulnerable range="lt">45.6.0</vulnerable>
+ </package>
+ <package name="mail-client/thunderbird" auto="yes" arch="*">
+ <unaffected range="ge">45.6.0</unaffected>
+ <vulnerable range="lt">45.6.0</vulnerable>
+ </package>
+ <package name="mail-client/thunderbird-bin" auto="yes" arch="*">
+ <unaffected range="ge">45.6.0</unaffected>
+ <vulnerable range="lt">45.6.0</vulnerable>
+ </package>
+ <package name="www-client/seamonkey" auto="yes" arch="*">
+ <unaffected range="ge">2.38</unaffected>
+ <vulnerable range="lt">2.38</vulnerable>
+ </package>
+ <package name="www-client/seamonkey-bin" auto="yes" arch="*">
+ <unaffected range="ge">2.38</unaffected>
+ <vulnerable range="lt">2.38</vulnerable>
+ </package>
+ </affected>
+ <background>
+ <p>Mozilla Firefox is a cross-platform web browser from Mozilla. The
+ Mozilla Thunderbird mail client is a redesign of the Mozilla Mail
+ component. The goal is to produce a cross-platform stand-alone mail
+ application using XUL (XML User Interface Language). SeaMonkey is a free
+ and open-source Internet suite. It is the continuation of the former
+ Mozilla Application Suite, based on the same source code.
+ </p>
+ </background>
+ <description>
+ <p>Multiple vulnerabilities have been discovered in Mozilla Firefox,
+ SeaMonkey, and Thunderbird. Please review the CVE identifiers referenced
+ below for details.
+ </p>
+ </description>
+ <impact type="normal">
+ <p>A remote attacker could possibly execute arbitrary code with the
+ privileges of the process or cause a Denial of Service condition via
+ multiple vectors.
+ </p>
+ </impact>
+ <workaround>
+ <p>There is no known workaround at this time.</p>
+ </workaround>
+ <resolution>
+ <p>All Firefox users should upgrade to the latest version:</p>
+
+ <code>
+ # emerge --sync
+ # emerge --ask --oneshot --verbose "&gt;=www-client/firefox-45.6.0"
+ </code>
+
+ <p>All Firefox-bin users should upgrade to the latest version:</p>
+
+ <code>
+ # emerge --sync
+ # emerge --ask --oneshot --verbose "&gt;=www-client/firefox-bin-45.6.0"
+ </code>
+
+ <p>All Thunderbird users should upgrade to the latest version:</p>
+
+ <code>
+ # emerge --sync
+ # emerge --ask --oneshot --verbose "&gt;=mail-client/thunderbird-45.6.0"
+ </code>
+
+ <p>All Thunderbird-bin users should upgrade to the latest version:</p>
+
+ <code>
+ # emerge --sync
+ # emerge --ask --oneshot --verbose
+ "&gt;=mail-client/thunderbird-bin-45.6.0"
+ </code>
+
+ <p>All SeaMonkey users should upgrade to the latest version:</p>
+
+ <code>
+ # emerge --sync
+ # emerge --ask --oneshot --verbose "&gt;=www-client/seamonkey-2.38"
+ </code>
+
+ <p>All SeaMonkey-bin users should upgrade to the latest version:</p>
+
+ <code>
+ # emerge --sync
+ # emerge --ask --oneshot --verbose "&gt;=www-client/seamonkey-bin-2.38"
+ </code>
+ </resolution>
+ <references>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8634">CVE-2014-8634</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8635">CVE-2014-8635</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8636">CVE-2014-8636</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8637">CVE-2014-8637</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8638">CVE-2014-8638</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8639">CVE-2014-8639</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8640">CVE-2014-8640</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8641">CVE-2014-8641</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8642">CVE-2014-8642</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0819">CVE-2015-0819</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0820">CVE-2015-0820</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0821">CVE-2015-0821</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0822">CVE-2015-0822</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0823">CVE-2015-0823</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0824">CVE-2015-0824</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0825">CVE-2015-0825</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0826">CVE-2015-0826</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0827">CVE-2015-0827</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0828">CVE-2015-0828</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0829">CVE-2015-0829</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0830">CVE-2015-0830</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0831">CVE-2015-0831</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0832">CVE-2015-0832</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0833">CVE-2015-0833</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0834">CVE-2015-0834</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0835">CVE-2015-0835</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-0836">CVE-2015-0836</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2804">CVE-2016-2804</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2805">CVE-2016-2805</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2806">CVE-2016-2806</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2807">CVE-2016-2807</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2808">CVE-2016-2808</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2809">CVE-2016-2809</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2810">CVE-2016-2810</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2811">CVE-2016-2811</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2812">CVE-2016-2812</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2813">CVE-2016-2813</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2814">CVE-2016-2814</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2816">CVE-2016-2816</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2817">CVE-2016-2817</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2820">CVE-2016-2820</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2827">CVE-2016-2827</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2830">CVE-2016-2830</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2835">CVE-2016-2835</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2836">CVE-2016-2836</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2837">CVE-2016-2837</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2838">CVE-2016-2838</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2839">CVE-2016-2839</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5250">CVE-2016-5250</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5251">CVE-2016-5251</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5252">CVE-2016-5252</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5253">CVE-2016-5253</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5254">CVE-2016-5254</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5255">CVE-2016-5255</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5256">CVE-2016-5256</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5257">CVE-2016-5257</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5258">CVE-2016-5258</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5259">CVE-2016-5259</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5260">CVE-2016-5260</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5261">CVE-2016-5261</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5262">CVE-2016-5262</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5263">CVE-2016-5263</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5264">CVE-2016-5264</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5265">CVE-2016-5265</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5266">CVE-2016-5266</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5267">CVE-2016-5267</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5268">CVE-2016-5268</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5270">CVE-2016-5270</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5271">CVE-2016-5271</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5272">CVE-2016-5272</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5273">CVE-2016-5273</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5274">CVE-2016-5274</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5275">CVE-2016-5275</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5276">CVE-2016-5276</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5277">CVE-2016-5277</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5278">CVE-2016-5278</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5279">CVE-2016-5279</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5280">CVE-2016-5280</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5281">CVE-2016-5281</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5282">CVE-2016-5282</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5283">CVE-2016-5283</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5284">CVE-2016-5284</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5290">CVE-2016-5290</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5291">CVE-2016-5291</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5293">CVE-2016-5293</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5294">CVE-2016-5294</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5296">CVE-2016-5296</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5297">CVE-2016-5297</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9064">CVE-2016-9064</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9066">CVE-2016-9066</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9074">CVE-2016-9074</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9079">CVE-2016-9079</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9893">CVE-2016-9893</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9895">CVE-2016-9895</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9897">CVE-2016-9897</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9898">CVE-2016-9898</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9899">CVE-2016-9899</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9900">CVE-2016-9900</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9901">CVE-2016-9901</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9902">CVE-2016-9902</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9904">CVE-2016-9904</uri>
+ <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9905">CVE-2016-9905</uri>
+ </references>
+ <metadata tag="requester" timestamp="Mon, 02 Jan 2017 23:32:38 +0000">b-man</metadata>
+ <metadata tag="submitter" timestamp="Tue, 03 Jan 2017 12:54:04 +0000">b-man</metadata>
+</glsa>