glsa-200608-07.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

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="/xsl/glsa.xsl" type="text/xsl"?>
<?xml-stylesheet href="/xsl/guide.xsl" type="text/xsl"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">

<glsa id="200608-07">
  <title>libTIFF: Multiple vulnerabilities</title>
  <synopsis>
    libTIFF contains several vulnerabilities that could result in arbitrary
    code execution.
  </synopsis>
  <product type="ebuild">tiff</product>
  <announced>August 04, 2006</announced>
  <revised>August 04, 2006: 01</revised>
  <bug>142383</bug>
  <access>remote</access>
  <affected>
    <package name="media-libs/tiff" auto="yes" arch="*">
      <unaffected range="ge">3.8.2-r2</unaffected>
      <vulnerable range="lt">3.8.2-r2</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    libTIFF provides support for reading and manipulating TIFF images.
    </p>
  </background>
  <description>
    <p>
    Tavis Ormandy of the Google Security Team discovered several heap and
    stack buffer overflows and other flaws in libTIFF. The affected parts
    include the TIFFFetchShortPair(), TIFFScanLineSize() and
    EstimateStripByteCounts() functions, and the PixarLog and NeXT RLE
    decoders.
    </p>
  </description>
  <impact type="normal">
    <p>
    A remote attacker could entice a user to open a specially crafted TIFF
    file, resulting in the possible execution of arbitrary code.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All libTIFF users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose &quot;&gt;=media-libs/tiff-3.8.2-r2&quot;</code>
  </resolution>
  <references>
    <uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3459">CVE-2006-3459</uri>
    <uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3460">CVE-2006-3460</uri>
    <uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3461">CVE-2006-3461</uri>
    <uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3462">CVE-2006-3462</uri>
    <uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3463">CVE-2006-3463</uri>
    <uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3464">CVE-2006-3464</uri>
    <uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3465">CVE-2006-3465</uri>
  </references>
  <metadata tag="submitter" timestamp="Thu, 03 Aug 2006 11:25:07 +0000">
    falco
  </metadata>
  <metadata tag="bugReady" timestamp="Fri, 04 Aug 2006 09:34:08 +0000">
    jaervosz
  </metadata>
</glsa>