summaryrefslogtreecommitdiff
blob: 24ad5f33407915500ceab3f62154022bb4af71e4 (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
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200903-21">
  <title>cURL: Arbitrary file access</title>
  <synopsis>
    A vulnerability in cURL may allow for arbitrary file access.
  </synopsis>
  <product type="ebuild">curl</product>
  <announced>2009-03-09</announced>
  <revised count="01">2009-03-09</revised>
  <bug>260361</bug>
  <access>remote</access>
  <affected>
    <package name="net-misc/curl" auto="yes" arch="*">
      <unaffected range="ge">7.19.4</unaffected>
      <vulnerable range="lt">7.19.4</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    cURL is a command line tool for transferring files with URL syntax,
    supporting numerous protocols.
    </p>
  </background>
  <description>
    <p>
    David Kierznowski reported that the redirect implementation accepts
    arbitrary Location values when CURLOPT_FOLLOWLOCATION is enabled.
    </p>
  </description>
  <impact type="normal">
    <p>
    A remote attacker could possibly exploit this vulnerability to make
    remote HTTP servers trigger arbitrary requests to intranet servers and
    read or overwrite arbitrary files via a redirect to a file: URL, or, if
    the libssh2 USE flag is enabled, execute arbitrary commands via a
    redirect to an scp: URL.
    </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.19.4"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0037">CVE-2009-0037</uri>
  </references>
  <metadata tag="requester" timestamp="2009-03-05T20:06:34Z">
    keytoaster
  </metadata>
  <metadata tag="submitter" timestamp="2009-03-05T23:20:10Z">
    keytoaster
  </metadata>
  <metadata tag="bugReady" timestamp="2009-03-06T22:09:58Z">
    p-y
  </metadata>
</glsa>