summaryrefslogtreecommitdiff
blob: 8b34c3c22891d55bb041728e426fc50ecd701e92 (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
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200903-28">
  <title>libpng: Multiple vulnerabilities</title>
  <synopsis>
    Multiple vulnerabilities were found in libpng, which might result in the
    execution of arbitrary code
  </synopsis>
  <product type="ebuild">libpng</product>
  <announced>2009-03-15</announced>
  <revised>2009-03-15: 01</revised>
  <bug>244808</bug>
  <bug>255231</bug>
  <bug>259578</bug>
  <access>remote</access>
  <affected>
    <package name="media-libs/libpng" auto="yes" arch="*">
      <unaffected range="ge">1.2.35</unaffected>
      <vulnerable range="lt">1.2.35</vulnerable>
    </package>
  </affected>
  <background>
    <p>
    libpng is the official PNG reference library used to read, write and
    manipulate PNG images.
    </p>
  </background>
  <description>
    <p>
    Multiple vulnerabilities were discovered in libpng:
    </p>
    <ul>
    <li>A
    memory leak bug was reported in png_handle_tEXt(), a function that is
    used while reading PNG images (CVE-2008-6218).</li>
    <li>A memory
    overwrite bug was reported by Jon Foster in png_check_keyword(), caused
    by writing overlong keywords to a PNG file (CVE-2008-5907).</li>
    <li>A
    memory corruption issue, caused by an incorrect handling of an out of
    memory condition has been reported by Tavis Ormandy of the Google
    Security Team. That vulnerability affects direct uses of
    png_read_png(), pCAL chunk and 16-bit gamma table handling
    (CVE-2009-0040).</li>
    </ul>
  </description>
  <impact type="normal">
    <p>
    A remote attacker may execute arbitrary code with the privileges of the
    user opening a specially crafted PNG file by exploiting the erroneous
    out-of-memory handling. An attacker may also exploit the
    png_check_keyword() error to set arbitrary memory locations to 0, if
    the application allows overlong, user-controlled keywords when writing
    PNG files. The png_handle_tEXT() vulnerability may be exploited by an
    attacker to potentially consume all memory on a users system when a
    specially crafted PNG file is opened.
    </p>
  </impact>
  <workaround>
    <p>
    There is no known workaround at this time.
    </p>
  </workaround>
  <resolution>
    <p>
    All libpng users should upgrade to the latest version:
    </p>
    <code>
    # emerge --sync
    # emerge --ask --oneshot --verbose "&gt;=media-libs/libpng-1.2.35"</code>
  </resolution>
  <references>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-5907">CVE-2008-5907</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-6218">CVE-2008-6218</uri>
    <uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-0040">CVE-2009-0040</uri>
  </references>
  <metadata tag="requester" timestamp="2009-01-11T18:45:00Z">
    craig
  </metadata>
  <metadata tag="submitter" timestamp="2009-02-13T19:13:22Z">
    mabi
  </metadata>
  <metadata tag="bugReady" timestamp="2009-03-13T19:09:44Z">
    p-y
  </metadata>
</glsa>