glsa-201402-04.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

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201402-04">
  <title>libwww-perl: Multiple vulnerabilities</title>
  <synopsis>Multiple vulnerabilities have been found in libwww-perl, the worst
    of which could allow attackers to execute arbitrary code.
  </synopsis>
  <product type="ebuild">libwww-perl</product>
  <announced>2014-02-04</announced>
  <revised count="1">2014-02-04</revised>
  <bug>329943</bug>
  <bug>386309</bug>
  <access>remote</access>
  <affected>
    <package name="dev-perl/libwww-perl" auto="yes" arch="*">
      <unaffected range="ge">6.30.0</unaffected>
      <vulnerable range="lt">6.30.0</vulnerable>
    </package>
  </affected>
  <background>
    <p>libwww is a collection of Perl modules providing a consistent interface
      to the World-Wide Web.
    </p>
  </background>
  <description>
    <p>Multiple vulnerabilities have been discovered in libwww-perl. Please
      review the CVE identifiers referenced below for details.
    </p>
  </description>
  <impact type="normal">
    <p>A remote attacker could entice a user to download a specially-crafted
      file with an application linked against libwww-perl, which could result
      in overwritten files or arbitrary code execution by writing to a dotfile
      in the user’s home directory (such as .bashrc). Additionally, a remote
      attacker could perform a Man-in-the-Middle attack.
    </p>
  </impact>
  <workaround>
    <p>There is no known workaround at this time.</p>
  </workaround>
  <resolution>
    <p>All libwww-perl users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=dev-perl/libwww-perl-6.30.0"
    </code>
    
    <p>NOTE: This is a legacy GLSA. Updates for all affected architectures are
      available since December 18, 2011. It is likely that your system is
      already no longer affected by this issue.
    </p>
    
  </resolution>
  <references>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-2253">CVE-2010-2253</uri>
    <uri link="https://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-0633">CVE-2011-0633</uri>
  </references>
  <metadata tag="requester" timestamp="2011-10-07T23:38:06Z">
    underling
  </metadata>
  <metadata tag="submitter" timestamp="2014-02-04T15:57:46Z">
    pinkbyte
  </metadata>
</glsa>