summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
Diffstat (limited to 'metadata/glsa/glsa-200608-07.xml')
-rw-r--r--metadata/glsa/glsa-200608-07.xml68
1 files changed, 68 insertions, 0 deletions
diff --git a/metadata/glsa/glsa-200608-07.xml b/metadata/glsa/glsa-200608-07.xml
new file mode 100644
index 000000000000..54970a0ccc62
--- /dev/null
+++ b/metadata/glsa/glsa-200608-07.xml
@@ -0,0 +1,68 @@
+<?xml version="1.0" encoding="utf-8"?>
+<!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>2006-08-04</announced>
+ <revised count="01">2006-08-04</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 "&gt;=media-libs/tiff-3.8.2-r2"</code>
+ </resolution>
+ <references>
+ <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3459">CVE-2006-3459</uri>
+ <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3460">CVE-2006-3460</uri>
+ <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3461">CVE-2006-3461</uri>
+ <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3462">CVE-2006-3462</uri>
+ <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3463">CVE-2006-3463</uri>
+ <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3464">CVE-2006-3464</uri>
+ <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-3465">CVE-2006-3465</uri>
+ </references>
+ <metadata tag="submitter" timestamp="2006-08-03T11:25:07Z">
+ falco
+ </metadata>
+ <metadata tag="bugReady" timestamp="2006-08-04T09:34:08Z">
+ jaervosz
+ </metadata>
+</glsa>