blob: ac6bec724d08e686de622807f0dc54a2722919e3 (
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
|
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200712-13">
<title>E2fsprogs: Multiple buffer overflows</title>
<synopsis>
Multiple heap-based buffer overflows in E2fsprogs could result in the
execution of arbitrary code.
</synopsis>
<product type="ebuild">e2fsprogs</product>
<announced>2007-12-18</announced>
<revised count="01">2007-12-18</revised>
<bug>201546</bug>
<access>remote</access>
<affected>
<package name="sys-fs/e2fsprogs" auto="yes" arch="*">
<unaffected range="ge">1.40.3</unaffected>
<vulnerable range="lt">1.40.3</vulnerable>
</package>
</affected>
<background>
<p>
E2fsprogs provides utilities for use with the ext2 and ext3 file
systems including the libext2fs library that allows user-level programs
to manipulate an ext2 or ext3 file system.
</p>
</background>
<description>
<p>
Rafal Wojtczuk (McAfee AVERT Research) discovered multiple integer
overflows in libext2fs, that are triggered when processing information
from within the file system, resulting in heap-based buffer overflows.
</p>
</description>
<impact type="normal">
<p>
An attacker could entice a user to process a specially-crafted ext2 or
ext3 file system image (with tools linking against libext2fs, e.g.
fsck, forensic tools or Xen's pygrub), possibly resulting in the
execution of arbitrary code with the privileges of the user running the
application.
</p>
</impact>
<workaround>
<p>
There is no known workaround at this time.
</p>
</workaround>
<resolution>
<p>
All E2fsprogs users should upgrade to the latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=sys-fs/e2fsprogs-1.40.3"</code>
</resolution>
<references>
<uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-5497">CVE-2007-5497</uri>
</references>
<metadata tag="requester" timestamp="2007-12-12T09:56:09Z">
rbu
</metadata>
<metadata tag="submitter" timestamp="2007-12-13T21:11:04Z">
rbu
</metadata>
<metadata tag="bugReady" timestamp="2007-12-13T23:03:39Z">
rbu
</metadata>
</glsa>
|