metadata/glsa/glsa-201908-01.xml


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

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201908-01">
  <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>2019-08-03</announced>
  <revised count="1">2019-08-03</revised>
  <bug>672904</bug>
  <bug>672910</bug>
  <bug>674668</bug>
  <bug>682698</bug>
  <bug>682702</bug>
  <access>remote</access>
  <affected>
    <package name="sys-devel/binutils" auto="yes" arch="*">
      <unaffected range="ge">2.32-r1</unaffected>
      <vulnerable range="lt">2.32-r1</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
      the referenced CVE identifiers for details.
    </p>
  </description>
  <impact type="normal">
    <p>A remote attacker, by enticing a user to compile/execute a specially
      crafted ELF, object, PE, or binary file, could possibly cause a Denial of
      Service condition or have other unspecified impacts.
    </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 "&gt;=sys-devel/binutils-2.32-r1"
    </code>
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-10372">CVE-2018-10372</uri>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-10373">CVE-2018-10373</uri>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-10534">CVE-2018-10534</uri>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-10535">CVE-2018-10535</uri>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-12641">CVE-2018-12641</uri>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-12697">CVE-2018-12697</uri>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-12698">CVE-2018-12698</uri>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-12699">CVE-2018-12699</uri>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-12700">CVE-2018-12700</uri>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-13033">CVE-2018-13033</uri>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-19931">CVE-2018-19931</uri>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-19932">CVE-2018-19932</uri>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-20002">CVE-2018-20002</uri>
    <uri link="https://nvd.nist.gov/vuln/detail/CVE-2018-20651">CVE-2018-20651</uri>
  </references>
  <metadata tag="requester" timestamp="2019-04-29T23:24:32Z">b-man</metadata>
  <metadata tag="submitter" timestamp="2019-08-03T11:22:15Z">b-man</metadata>
</glsa>