summaryrefslogtreecommitdiff
blob: 6bc6ba8fa07dfd5e4c8a6106e84be3085df6ff16 (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
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="201406-02">
  <title>libarchive: Multiple vulnerabilities</title>
  <synopsis>Multiple vulnerabilities have been found in libarchive, some of
    which may allow execution of arbitrary code.
  </synopsis>
  <product type="ebuild">libarchive</product>
  <announced>June 01, 2014</announced>
  <revised>June 01, 2014: 1</revised>
  <bug>366687</bug>
  <bug>463632</bug>
  <access>remote</access>
  <affected>
    <package name="app-arch/libarchive" auto="yes" arch="*">
      <unaffected range="ge">3.1.2-r1</unaffected>
      <vulnerable range="lt">3.1.2-r1</vulnerable>
    </package>
  </affected>
  <background>
    <p>libarchive is a library for manipulating different streaming archive
      formats, including certain tar variants, several cpio formats, and both
      BSD and GNU ar variants.
    </p>
  </background>
  <description>
    <p>Multiple vulnerabilities have been discovered in libarchive. Please
      review the CVE identifiers referenced below for details.
    </p>
  </description>
  <impact type="normal">
    <p>A remote attacker could entice a user or automated process to open a
      specially crafted archive using an application linked against libarchive,
      possibly resulting in execution of arbitrary code with the privileges of
      the process or a Denial of Service condition.
    </p>
  </impact>
  <workaround>
    <p>There is no known workaround at this time.</p>
  </workaround>
  <resolution>
    <p>All libarchive users should upgrade to the latest version:</p>
    
    <code>
      # emerge --sync
      # emerge --ask --oneshot --verbose "&gt;=app-arch/libarchive-3.1.2-r1"
    </code>
    
    <p>Packages which depend on this library may need to be recompiled. Tools
      such as revdep-rebuild may assist in identifying some of these packages.
    </p>
  </resolution>
  <references>
    <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2010-4666">CVE-2010-4666</uri>
    <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-1777">CVE-2011-1777</uri>
    <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-1778">CVE-2011-1778</uri>
    <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2011-1779">CVE-2011-1779</uri>
    <uri link="http://nvd.nist.gov/nvd.cfm?cvename=CVE-2013-0211">CVE-2013-0211</uri>
  </references>
  <metadata tag="requester" timestamp="Sun, 22 Jan 2012 19:10:06 +0000">
    underling
  </metadata>
  <metadata tag="submitter" timestamp="Sun, 01 Jun 2014 15:10:38 +0000">ackle</metadata>
</glsa>