1 |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
2 |
Gentoo Linux Security Advisory GLSA 201605-06 |
3 |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
4 |
https://security.gentoo.org/ |
5 |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
6 |
|
7 |
Severity: Normal |
8 |
Title: Mozilla Products: Multiple vulnerabilities |
9 |
Date: May 31, 2016 |
10 |
Bugs: #549356, #557590, #559186, #561246, #563230, #564834, |
11 |
#573074, #574596, #576862 |
12 |
ID: 201605-06 |
13 |
|
14 |
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - |
15 |
|
16 |
Synopsis |
17 |
======== |
18 |
|
19 |
Multiple vulnerabilities have been found in Firefox, Thunderbird, |
20 |
Network Security Services (NSS), and NetScape Portable Runtime (NSPR) |
21 |
with the worst of which may allow remote execution of arbitrary code. |
22 |
|
23 |
Background |
24 |
========== |
25 |
|
26 |
Mozilla Firefox is an open-source web browser, Mozilla Thunderbird an |
27 |
open-source email client, and the Network Security Service (NSS) is a |
28 |
library implementing security features like SSL v.2/v.3, TLS, PKCS #5, |
29 |
PKCS #7, PKCS #11, PKCS #12, S/MIME and X.509 certificates. The |
30 |
SeaMonkey project is a community effort to deliver production-quality |
31 |
releases of code derived from the application formerly known as |
32 |
'Mozilla Application Suite'. |
33 |
|
34 |
Affected packages |
35 |
================= |
36 |
|
37 |
------------------------------------------------------------------- |
38 |
Package / Vulnerable / Unaffected |
39 |
------------------------------------------------------------------- |
40 |
1 dev-libs/nspr < 4.12 >= 4.12 |
41 |
2 dev-libs/nss < 3.22.2 >= 3.22.2 |
42 |
3 mail-client/thunderbird < 38.7.0 >= 38.7.0 |
43 |
4 mail-client/thunderbird-bin |
44 |
< 38.7.0 >= 38.7.0 |
45 |
5 www-client/firefox < 38.7.0 >= 38.7.0 |
46 |
6 www-client/firefox-bin < 38.7.0 >= 38.7.0 |
47 |
------------------------------------------------------------------- |
48 |
6 affected packages |
49 |
|
50 |
Description |
51 |
=========== |
52 |
|
53 |
Multiple vulnerabilities have been discovered in Firefox, NSS, NSPR, |
54 |
and Thunderbird. Please review the CVE identifiers referenced below for |
55 |
details. |
56 |
|
57 |
Impact |
58 |
====== |
59 |
|
60 |
A remote attacker could entice a user to view a specially crafted web |
61 |
page or email, possibly resulting in execution of arbitrary code or a |
62 |
Denial of Service condition. Furthermore, a remote attacker may be able |
63 |
to perform Man-in-the-Middle attacks, obtain sensitive information, |
64 |
spoof the address bar, conduct clickjacking attacks, bypass security |
65 |
restrictions and protection mechanisms, or have other unspecified |
66 |
impacts. |
67 |
|
68 |
Workaround |
69 |
========== |
70 |
|
71 |
There is no known workaround at this time. |
72 |
|
73 |
Resolution |
74 |
========== |
75 |
|
76 |
All NSS users should upgrade to the latest version: |
77 |
|
78 |
# emerge --sync |
79 |
# emerge --ask --oneshot --verbose ">=dev-libs/nss-3.22.2" |
80 |
|
81 |
All Thunderbird users should upgrade to the latest version: |
82 |
|
83 |
# emerge --sync |
84 |
# emerge --ask --oneshot --verbose ">=mail-client/thunderbird-38.7.0" |
85 |
|
86 |
All users of the Thunderbird binary package should upgrade to the |
87 |
latest version: |
88 |
|
89 |
# emerge --sync |
90 |
# emerge --ask --oneshot -v ">=mail-client/thunderbird-bin-38.7.0" |
91 |
|
92 |
All Firefox 38.7.x users should upgrade to the latest version: |
93 |
|
94 |
# emerge --sync |
95 |
# emerge --ask --oneshot --verbose ">=www-client/firefox-38.7.0" |
96 |
|
97 |
All users of the Firefox 38.7.x binary package should upgrade to the |
98 |
latest version: |
99 |
|
100 |
# emerge --sync |
101 |
# emerge --ask --oneshot --verbose ">=www-client/firefox-bin-38.7.0" |
102 |
|
103 |
References |
104 |
========== |
105 |
|
106 |
[ 1 ] CVE-2015-2708 |
107 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2708 |
108 |
[ 2 ] CVE-2015-2708 |
109 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2708 |
110 |
[ 3 ] CVE-2015-2709 |
111 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2709 |
112 |
[ 4 ] CVE-2015-2709 |
113 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2709 |
114 |
[ 5 ] CVE-2015-2710 |
115 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2710 |
116 |
[ 6 ] CVE-2015-2710 |
117 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2710 |
118 |
[ 7 ] CVE-2015-2711 |
119 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2711 |
120 |
[ 8 ] CVE-2015-2711 |
121 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2711 |
122 |
[ 9 ] CVE-2015-2712 |
123 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2712 |
124 |
[ 10 ] CVE-2015-2712 |
125 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2712 |
126 |
[ 11 ] CVE-2015-2713 |
127 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2713 |
128 |
[ 12 ] CVE-2015-2713 |
129 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2713 |
130 |
[ 13 ] CVE-2015-2714 |
131 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2714 |
132 |
[ 14 ] CVE-2015-2714 |
133 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2714 |
134 |
[ 15 ] CVE-2015-2715 |
135 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2715 |
136 |
[ 16 ] CVE-2015-2715 |
137 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2715 |
138 |
[ 17 ] CVE-2015-2716 |
139 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2716 |
140 |
[ 18 ] CVE-2015-2716 |
141 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2716 |
142 |
[ 19 ] CVE-2015-2717 |
143 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2717 |
144 |
[ 20 ] CVE-2015-2717 |
145 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2717 |
146 |
[ 21 ] CVE-2015-2718 |
147 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2718 |
148 |
[ 22 ] CVE-2015-2718 |
149 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-2718 |
150 |
[ 23 ] CVE-2015-4473 |
151 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4473 |
152 |
[ 24 ] CVE-2015-4473 |
153 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4473 |
154 |
[ 25 ] CVE-2015-4474 |
155 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4474 |
156 |
[ 26 ] CVE-2015-4474 |
157 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4474 |
158 |
[ 27 ] CVE-2015-4475 |
159 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4475 |
160 |
[ 28 ] CVE-2015-4475 |
161 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4475 |
162 |
[ 29 ] CVE-2015-4477 |
163 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4477 |
164 |
[ 30 ] CVE-2015-4477 |
165 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4477 |
166 |
[ 31 ] CVE-2015-4478 |
167 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4478 |
168 |
[ 32 ] CVE-2015-4478 |
169 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4478 |
170 |
[ 33 ] CVE-2015-4479 |
171 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4479 |
172 |
[ 34 ] CVE-2015-4479 |
173 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4479 |
174 |
[ 35 ] CVE-2015-4480 |
175 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4480 |
176 |
[ 36 ] CVE-2015-4480 |
177 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4480 |
178 |
[ 37 ] CVE-2015-4481 |
179 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4481 |
180 |
[ 38 ] CVE-2015-4481 |
181 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4481 |
182 |
[ 39 ] CVE-2015-4482 |
183 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4482 |
184 |
[ 40 ] CVE-2015-4482 |
185 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4482 |
186 |
[ 41 ] CVE-2015-4483 |
187 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4483 |
188 |
[ 42 ] CVE-2015-4483 |
189 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4483 |
190 |
[ 43 ] CVE-2015-4484 |
191 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4484 |
192 |
[ 44 ] CVE-2015-4484 |
193 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4484 |
194 |
[ 45 ] CVE-2015-4485 |
195 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4485 |
196 |
[ 46 ] CVE-2015-4485 |
197 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4485 |
198 |
[ 47 ] CVE-2015-4486 |
199 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4486 |
200 |
[ 48 ] CVE-2015-4486 |
201 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4486 |
202 |
[ 49 ] CVE-2015-4487 |
203 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4487 |
204 |
[ 50 ] CVE-2015-4487 |
205 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4487 |
206 |
[ 51 ] CVE-2015-4488 |
207 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4488 |
208 |
[ 52 ] CVE-2015-4488 |
209 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4488 |
210 |
[ 53 ] CVE-2015-4489 |
211 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4489 |
212 |
[ 54 ] CVE-2015-4489 |
213 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4489 |
214 |
[ 55 ] CVE-2015-4490 |
215 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4490 |
216 |
[ 56 ] CVE-2015-4490 |
217 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4490 |
218 |
[ 57 ] CVE-2015-4491 |
219 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4491 |
220 |
[ 58 ] CVE-2015-4491 |
221 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4491 |
222 |
[ 59 ] CVE-2015-4492 |
223 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4492 |
224 |
[ 60 ] CVE-2015-4492 |
225 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4492 |
226 |
[ 61 ] CVE-2015-4493 |
227 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4493 |
228 |
[ 62 ] CVE-2015-4493 |
229 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-4493 |
230 |
[ 63 ] CVE-2015-7181 |
231 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-7181 |
232 |
[ 64 ] CVE-2015-7182 |
233 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-7182 |
234 |
[ 65 ] CVE-2015-7183 |
235 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2015-7183 |
236 |
[ 66 ] CVE-2016-1523 |
237 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1523 |
238 |
[ 67 ] CVE-2016-1523 |
239 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1523 |
240 |
[ 68 ] CVE-2016-1930 |
241 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1930 |
242 |
[ 69 ] CVE-2016-1930 |
243 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1930 |
244 |
[ 70 ] CVE-2016-1931 |
245 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1931 |
246 |
[ 71 ] CVE-2016-1931 |
247 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1931 |
248 |
[ 72 ] CVE-2016-1933 |
249 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1933 |
250 |
[ 73 ] CVE-2016-1933 |
251 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1933 |
252 |
[ 74 ] CVE-2016-1935 |
253 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1935 |
254 |
[ 75 ] CVE-2016-1935 |
255 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1935 |
256 |
[ 76 ] CVE-2016-1937 |
257 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1937 |
258 |
[ 77 ] CVE-2016-1937 |
259 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1937 |
260 |
[ 78 ] CVE-2016-1938 |
261 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1938 |
262 |
[ 79 ] CVE-2016-1938 |
263 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1938 |
264 |
[ 80 ] CVE-2016-1939 |
265 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1939 |
266 |
[ 81 ] CVE-2016-1939 |
267 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1939 |
268 |
[ 82 ] CVE-2016-1940 |
269 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1940 |
270 |
[ 83 ] CVE-2016-1940 |
271 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1940 |
272 |
[ 84 ] CVE-2016-1941 |
273 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1941 |
274 |
[ 85 ] CVE-2016-1941 |
275 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1941 |
276 |
[ 86 ] CVE-2016-1942 |
277 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1942 |
278 |
[ 87 ] CVE-2016-1942 |
279 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1942 |
280 |
[ 88 ] CVE-2016-1943 |
281 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1943 |
282 |
[ 89 ] CVE-2016-1943 |
283 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1943 |
284 |
[ 90 ] CVE-2016-1944 |
285 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1944 |
286 |
[ 91 ] CVE-2016-1944 |
287 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1944 |
288 |
[ 92 ] CVE-2016-1945 |
289 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1945 |
290 |
[ 93 ] CVE-2016-1945 |
291 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1945 |
292 |
[ 94 ] CVE-2016-1946 |
293 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1946 |
294 |
[ 95 ] CVE-2016-1946 |
295 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1946 |
296 |
[ 96 ] CVE-2016-1947 |
297 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1947 |
298 |
[ 97 ] CVE-2016-1947 |
299 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1947 |
300 |
[ 98 ] CVE-2016-1948 |
301 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1948 |
302 |
[ 99 ] CVE-2016-1948 |
303 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1948 |
304 |
[ 100 ] CVE-2016-1949 |
305 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1949 |
306 |
[ 101 ] CVE-2016-1949 |
307 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1949 |
308 |
[ 102 ] CVE-2016-1950 |
309 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1950 |
310 |
[ 103 ] CVE-2016-1950 |
311 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1950 |
312 |
[ 104 ] CVE-2016-1952 |
313 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1952 |
314 |
[ 105 ] CVE-2016-1952 |
315 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1952 |
316 |
[ 106 ] CVE-2016-1953 |
317 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1953 |
318 |
[ 107 ] CVE-2016-1953 |
319 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1953 |
320 |
[ 108 ] CVE-2016-1954 |
321 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1954 |
322 |
[ 109 ] CVE-2016-1954 |
323 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1954 |
324 |
[ 110 ] CVE-2016-1955 |
325 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1955 |
326 |
[ 111 ] CVE-2016-1955 |
327 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1955 |
328 |
[ 112 ] CVE-2016-1956 |
329 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1956 |
330 |
[ 113 ] CVE-2016-1956 |
331 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1956 |
332 |
[ 114 ] CVE-2016-1957 |
333 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1957 |
334 |
[ 115 ] CVE-2016-1957 |
335 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1957 |
336 |
[ 116 ] CVE-2016-1958 |
337 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1958 |
338 |
[ 117 ] CVE-2016-1958 |
339 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1958 |
340 |
[ 118 ] CVE-2016-1959 |
341 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1959 |
342 |
[ 119 ] CVE-2016-1959 |
343 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1959 |
344 |
[ 120 ] CVE-2016-1960 |
345 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1960 |
346 |
[ 121 ] CVE-2016-1960 |
347 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1960 |
348 |
[ 122 ] CVE-2016-1961 |
349 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1961 |
350 |
[ 123 ] CVE-2016-1961 |
351 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1961 |
352 |
[ 124 ] CVE-2016-1962 |
353 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1962 |
354 |
[ 125 ] CVE-2016-1962 |
355 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1962 |
356 |
[ 126 ] CVE-2016-1963 |
357 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1963 |
358 |
[ 127 ] CVE-2016-1963 |
359 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1963 |
360 |
[ 128 ] CVE-2016-1964 |
361 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1964 |
362 |
[ 129 ] CVE-2016-1964 |
363 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1964 |
364 |
[ 130 ] CVE-2016-1965 |
365 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1965 |
366 |
[ 131 ] CVE-2016-1965 |
367 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1965 |
368 |
[ 132 ] CVE-2016-1966 |
369 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1966 |
370 |
[ 133 ] CVE-2016-1966 |
371 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1966 |
372 |
[ 134 ] CVE-2016-1967 |
373 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1967 |
374 |
[ 135 ] CVE-2016-1967 |
375 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1967 |
376 |
[ 136 ] CVE-2016-1968 |
377 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1968 |
378 |
[ 137 ] CVE-2016-1968 |
379 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1968 |
380 |
[ 138 ] CVE-2016-1969 |
381 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1969 |
382 |
[ 139 ] CVE-2016-1969 |
383 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1969 |
384 |
[ 140 ] CVE-2016-1970 |
385 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1970 |
386 |
[ 141 ] CVE-2016-1970 |
387 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1970 |
388 |
[ 142 ] CVE-2016-1971 |
389 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1971 |
390 |
[ 143 ] CVE-2016-1971 |
391 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1971 |
392 |
[ 144 ] CVE-2016-1972 |
393 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1972 |
394 |
[ 145 ] CVE-2016-1972 |
395 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1972 |
396 |
[ 146 ] CVE-2016-1973 |
397 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1973 |
398 |
[ 147 ] CVE-2016-1973 |
399 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1973 |
400 |
[ 148 ] CVE-2016-1974 |
401 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1974 |
402 |
[ 149 ] CVE-2016-1974 |
403 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1974 |
404 |
[ 150 ] CVE-2016-1975 |
405 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1975 |
406 |
[ 151 ] CVE-2016-1975 |
407 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1975 |
408 |
[ 152 ] CVE-2016-1976 |
409 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1976 |
410 |
[ 153 ] CVE-2016-1976 |
411 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1976 |
412 |
[ 154 ] CVE-2016-1977 |
413 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1977 |
414 |
[ 155 ] CVE-2016-1977 |
415 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1977 |
416 |
[ 156 ] CVE-2016-1978 |
417 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1978 |
418 |
[ 157 ] CVE-2016-1978 |
419 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1978 |
420 |
[ 158 ] CVE-2016-1979 |
421 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1979 |
422 |
[ 159 ] CVE-2016-1979 |
423 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-1979 |
424 |
[ 160 ] CVE-2016-2790 |
425 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2790 |
426 |
[ 161 ] CVE-2016-2790 |
427 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2790 |
428 |
[ 162 ] CVE-2016-2791 |
429 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2791 |
430 |
[ 163 ] CVE-2016-2791 |
431 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2791 |
432 |
[ 164 ] CVE-2016-2792 |
433 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2792 |
434 |
[ 165 ] CVE-2016-2792 |
435 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2792 |
436 |
[ 166 ] CVE-2016-2793 |
437 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2793 |
438 |
[ 167 ] CVE-2016-2793 |
439 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2793 |
440 |
[ 168 ] CVE-2016-2794 |
441 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2794 |
442 |
[ 169 ] CVE-2016-2794 |
443 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2794 |
444 |
[ 170 ] CVE-2016-2795 |
445 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2795 |
446 |
[ 171 ] CVE-2016-2795 |
447 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2795 |
448 |
[ 172 ] CVE-2016-2796 |
449 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2796 |
450 |
[ 173 ] CVE-2016-2796 |
451 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2796 |
452 |
[ 174 ] CVE-2016-2797 |
453 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2797 |
454 |
[ 175 ] CVE-2016-2797 |
455 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2797 |
456 |
[ 176 ] CVE-2016-2798 |
457 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2798 |
458 |
[ 177 ] CVE-2016-2798 |
459 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2798 |
460 |
[ 178 ] CVE-2016-2799 |
461 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2799 |
462 |
[ 179 ] CVE-2016-2799 |
463 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2799 |
464 |
[ 180 ] CVE-2016-2800 |
465 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2800 |
466 |
[ 181 ] CVE-2016-2800 |
467 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2800 |
468 |
[ 182 ] CVE-2016-2801 |
469 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2801 |
470 |
[ 183 ] CVE-2016-2801 |
471 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2801 |
472 |
[ 184 ] CVE-2016-2802 |
473 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2802 |
474 |
[ 185 ] CVE-2016-2802 |
475 |
http://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-2802 |
476 |
|
477 |
Availability |
478 |
============ |
479 |
|
480 |
This GLSA and any updates to it are available for viewing at |
481 |
the Gentoo Security Website: |
482 |
|
483 |
https://security.gentoo.org/glsa/201605-06 |
484 |
|
485 |
Concerns? |
486 |
========= |
487 |
|
488 |
Security is a primary focus of Gentoo Linux and ensuring the |
489 |
confidentiality and security of our users' machines is of utmost |
490 |
importance to us. Any security concerns should be addressed to |
491 |
security@g.o or alternatively, you may file a bug at |
492 |
https://bugs.gentoo.org. |
493 |
|
494 |
License |
495 |
======= |
496 |
|
497 |
Copyright 2016 Gentoo Foundation, Inc; referenced text |
498 |
belongs to its owner(s). |
499 |
|
500 |
The contents of this document are licensed under the |
501 |
Creative Commons - Attribution / Share Alike license. |
502 |
|
503 |
http://creativecommons.org/licenses/by-sa/2.5 |