blob: cd90ca7bb851b6e6f049e4f59887db08c7ab22c3 (
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
|
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200804-15">
<title>libpng: Execution of arbitrary code</title>
<synopsis>
A vulnerability in libpng may allow for execution of arbitrary code in
certain applications that handle untrusted images.
</synopsis>
<product type="ebuild">libpng</product>
<announced>2008-04-15</announced>
<revised>2008-04-15: 01</revised>
<bug>217047</bug>
<access>remote</access>
<affected>
<package name="media-libs/libpng" auto="yes" arch="*">
<unaffected range="ge">1.2.26-r1</unaffected>
<vulnerable range="lt">1.2.26-r1</vulnerable>
</package>
</affected>
<background>
<p>
libpng is a free ANSI C library used to process and manipulate PNG
images.
</p>
</background>
<description>
<p>
Tavis Ormandy of the Google Security Team discovered that libpng does
not handle zero-length unknown chunks in PNG files correctly, which
might lead to memory corruption in applications that call
png_set_read_user_chunk_fn() or png_set_keep_unknown_chunks().
</p>
</description>
<impact type="high">
<p>
A remote attacker could entice a user or automated system to process a
specially crafted PNG image in an application using libpng and possibly
execute arbitrary code with the privileges of the user running the
application. Note that processing of unknown chunks is disabled by
default in most PNG applications, but some such as ImageMagick are
affected.
</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 ">=media-libs/libpng-1.2.26-r1"</code>
</resolution>
<references>
<uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1382">CVE-2008-1382</uri>
</references>
<metadata tag="requester" timestamp="2008-04-14T01:44:56Z">
rbu
</metadata>
<metadata tag="submitter" timestamp="2008-04-14T01:49:03Z">
rbu
</metadata>
<metadata tag="bugReady" timestamp="2008-04-14T08:39:38Z">
p-y
</metadata>
</glsa>
|