metadata/glsa/glsa-201701-47.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
70
71
72
73
74
75
76
77
78
79
80

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201701-47">
  <title>cURL: Multiple vulnerabilities</title>
  <synopsis>Multiple vulnerabilities have been found in cURL, the worst of
    which could allow remote attackers to execute arbitrary code.
  </synopsis>
  <product type="ebuild">curl</product>
  <announced>2017-01-19</announced>
  <revised count="01">2017-01-19</revised>
  <bug>536014</bug>
  <bug>573102</bug>
  <bug>583394</bug>
  <bug>590482</bug>
  <bug>592974</bug>
  <bug>593716</bug>
  <bug>597760</bug>
  <bug>603370</bug>
  <bug>603574</bug>
  <access>remote</access>
  <affected>
    <package name="net-misc/curl" auto="yes" arch="*">
      <unaffected range="ge">7.52.1</unaffected>
      <vulnerable range="lt">7.52.1</vulnerable>
    </package>
  </affected>
  <background>
    <p>cURL is a tool and libcurl is a library for transferring data with URL
      syntax.
    </p>
  </background>
  <description>
    <p>Multiple vulnerabilities have been discovered in cURL. Please review the
      CVE identifiers and bug reports referenced for details.
    </p>
  </description>
  <impact type="normal">
    <p>Remote attackers could conduct a Man-in-the-Middle attack to obtain
      sensitive information, cause a Denial of Service condition, or execute
      arbitrary code.
    </p>
  </impact>
  <workaround>
    <p>There is no known workaround at this time.</p>
  </workaround>
  <resolution>
    <p>All cURL users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=net-misc/curl-7.52.1"
    </code>
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8150">CVE-2014-8150</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2014-8151">CVE-2014-8151</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-0755">CVE-2016-0755</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-3739">CVE-2016-3739</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5419">CVE-2016-5419</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5420">CVE-2016-5420</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-5421">CVE-2016-5421</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-7141">CVE-2016-7141</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-7167">CVE-2016-7167</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-8615">CVE-2016-8615</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-8616">CVE-2016-8616</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-8617">CVE-2016-8617</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-8618">CVE-2016-8618</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-8619">CVE-2016-8619</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-8620">CVE-2016-8620</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-8621">CVE-2016-8621</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-8622">CVE-2016-8622</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-8623">CVE-2016-8623</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-8624">CVE-2016-8624</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-8625">CVE-2016-8625</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9586">CVE-2016-9586</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2016-9594">CVE-2016-9594</uri>
  </references>
  <metadata tag="requester" timestamp="2016-07-01T05:35:33Z">b-man</metadata>
  <metadata tag="submitter" timestamp="2017-01-19T19:23:08Z">b-man</metadata>
</glsa>