blob: e71b0cbf1210361d6bd8d1e6ee2a7f4c42f6d852 (
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
|
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200504-06">
<title>sharutils: Insecure temporary file creation</title>
<synopsis>
The unshar utility is vulnerable to symlink attacks, potentially allowing a
local user to overwrite arbitrary files.
</synopsis>
<product type="ebuild">sharutils</product>
<announced>2005-04-06</announced>
<revised count="01">2005-04-06</revised>
<bug>87939</bug>
<access>local</access>
<affected>
<package name="app-arch/sharutils" auto="yes" arch="*">
<unaffected range="ge">4.2.1-r11</unaffected>
<vulnerable range="lt">4.2.1-r11</vulnerable>
</package>
</affected>
<background>
<p>
sharutils is a collection of tools to deal with shar archives.
</p>
</background>
<description>
<p>
Joey Hess has discovered that the program unshar, which is a part
of sharutils, creates temporary files in a world-writable directory
with predictable names.
</p>
</description>
<impact type="normal">
<p>
A local attacker could create symbolic links in the temporary
files directory, pointing to a valid file somewhere on the filesystem.
When unshar is executed, this would result in the file being
overwritten with the rights of the user running the utility, which
could be the root user.
</p>
</impact>
<workaround>
<p>
There is no known workaround at this time.
</p>
</workaround>
<resolution>
<p>
All sharutils users should upgrade to the latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=app-arch/sharutils-4.2.1-r11"</code>
</resolution>
<references>
<uri link="https://www.ubuntulinux.org/support/documentation/usn/usn-104-1">Ubuntu Advisory</uri>
</references>
<metadata tag="requester" timestamp="2005-04-05T07:42:03Z">
koon
</metadata>
<metadata tag="submitter" timestamp="2005-04-05T13:07:06Z">
lewk
</metadata>
<metadata tag="bugReady" timestamp="2005-04-06T20:15:09Z">
lewk
</metadata>
</glsa>
|