blob: a9c6b335bcb6d47b9a2de66ed5e2badbd94abf29 (
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
|
<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE glsa SYSTEM "http://www.gentoo.org/dtd/glsa.dtd">
<glsa id="200701-06">
<title>w3m: Format string vulnerability</title>
<synopsis>
w3m does not correctly handle format string specifiers in SSL certificates.
</synopsis>
<product type="ebuild">w3m</product>
<announced>2007-01-12</announced>
<revised>2007-01-12: 01</revised>
<bug>159145</bug>
<access>remote</access>
<affected>
<package name="www-client/w3m" auto="yes" arch="*">
<unaffected range="ge">0.5.1-r4</unaffected>
<vulnerable range="lt">0.5.1-r4</vulnerable>
</package>
</affected>
<background>
<p>
w3m is a multi-platform text-based web browser.
</p>
</background>
<description>
<p>
w3m in -dump or -backend mode does not correctly handle printf() format
string specifiers in the Common Name (CN) field of an X.509 SSL
certificate.
</p>
</description>
<impact type="normal">
<p>
An attacker could entice a user to visit a malicious website that would
load a specially crafted X.509 SSL certificate containing "%n" or other
format string specifiers, possibly resulting in the execution of
arbitrary code with the rights of the user running w3m.
</p>
</impact>
<workaround>
<p>
There is no known workaround at this time.
</p>
</workaround>
<resolution>
<p>
All w3m users should upgrade to the latest version:
</p>
<code>
# emerge --sync
# emerge --ask --oneshot --verbose ">=www-client/w3m-0.5.1-r4"</code>
</resolution>
<references>
<uri link="https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6772">CVE-2006-6772</uri>
</references>
<metadata tag="submitter" timestamp="2007-01-11T00:57:23Z">
aetius
</metadata>
<metadata tag="bugReady" timestamp="2007-01-11T11:00:25Z">
DerCorny
</metadata>
</glsa>
|
GitWeb
