blob: 49a6314f5c8fe30d4e985f573732d0b276e9ff84 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
|
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201709-02">
<title>Binutils: Multiple vulnerabilities</title>
<synopsis>Multiple vulnerabilities have been found in Binutils, the worst of
which may allow remote attackers to cause a Denial of Service condition.
</synopsis>
<product type="ebuild">binutils</product>
<announced>2017-09-17</announced>
<revised count="1">2017-09-17</revised>
<bug>618006</bug>
<bug>618514</bug>
<bug>618516</bug>
<bug>618520</bug>
<bug>618826</bug>
<bug>621130</bug>
<bug>624524</bug>
<bug>624702</bug>
<access>remote</access>
<affected>
<package name="sys-devel/binutils" auto="yes" arch="*">
<unaffected range="ge">2.28.1</unaffected>
<vulnerable range="lt">2.28.1</vulnerable>
</package>
</affected>
<background>
<p>The GNU Binutils are a collection of tools to create, modify and analyse
binary files. Many of the files use BFD, the Binary File Descriptor
library, to do low-level manipulation.
</p>
</background>
<description>
<p>Multiple vulnerabilities have been discovered in Binutils. Please review
References for additional information.
</p>
</description>
<impact type="normal">
<p>A remote attacker, by enticing a user to compile/execute a specially
crafted ELF file, PE File, or binary file, could possibly cause a Denial
of Service condition.
</p>
</impact>
<workaround>
<p>There is no known workaround at this time.</p>
</workaround>
<resolution>
<p>All Binutils users should upgrade to the latest version:</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=sys-devel/binutils-2.28.1"
</code>
</resolution>
<references>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-6965">
CVE-2017-6965
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-6966">
CVE-2017-6966
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-6969">
CVE-2017-6969
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-7614">
CVE-2017-7614
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-8392">
CVE-2017-8392
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-8393">
CVE-2017-8393
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-8394">
CVE-2017-8394
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-8395">
CVE-2017-8395
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-8396">
CVE-2017-8396
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-8397">
CVE-2017-8397
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-8398">
CVE-2017-8398
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-8421">
CVE-2017-8421
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9038">
CVE-2017-9038
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9039">
CVE-2017-9039
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9040">
CVE-2017-9040
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9041">
CVE-2017-9041
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9042">
CVE-2017-9042
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9742">
CVE-2017-9742
</uri>
<uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2017-9954">
CVE-2017-9954
</uri>
</references>
<metadata tag="requester" timestamp="2017-09-16T22:31:03Z">b-man</metadata>
<metadata tag="submitter" timestamp="2017-09-17T15:30:04Z">chrisadr</metadata>
</glsa>
|
