blob: 6c7708a2a0111cc388ee926b401a21ec6bdd6c24 (
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
|
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200510-15">
<title>Lynx: Buffer overflow in NNTP processing</title>
<synopsis>
Lynx contains a buffer overflow that may be exploited to execute arbitrary
code.
</synopsis>
<product type="ebuild">Lynx</product>
<announced>2005-10-17</announced>
<revised count="01">2005-10-17</revised>
<bug>108451</bug>
<access>remote</access>
<affected>
<package name="www-client/lynx" auto="yes" arch="*">
<unaffected range="ge">2.8.5-r1</unaffected>
<vulnerable range="lt">2.8.5-r1</vulnerable>
</package>
</affected>
<background>
<p>
Lynx is a text-mode browser for the World Wide Web. It supports
multiple URL types, including HTTP and NNTP URLs.
</p>
</background>
<description>
<p>
When accessing a NNTP URL, Lynx connects to a NNTP server and
retrieves information about the available articles in the target
newsgroup. Ulf Harnhammar discovered a buffer overflow in a function
that handles the escaping of special characters.
</p>
</description>
<impact type="normal">
<p>
An attacker could setup a malicious NNTP server and entice a user
to access it using Lynx (either by creating NNTP links on a web page or
by forcing a redirect for Lynx users). The data returned by the NNTP
server would trigger the buffer overflow and execute arbitrary code
with the rights of the user running Lynx.
</p>
</impact>
<workaround>
<p>
There is no known workaround at this time.
</p>
</workaround>
<resolution>
<p>
All Lynx users should upgrade to the latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=www-client/lynx-2.8.5-r1"</code>
</resolution>
<references>
<uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CAN-2005-3120">CAN-2005-3120</uri>
</references>
<metadata tag="submitter" timestamp="2005-10-15T09:30:52Z">
koon
</metadata>
<metadata tag="bugReady" timestamp="2005-10-17T12:46:58Z">
koon
</metadata>
</glsa>
|