blob: bc4e8bd85df498a41a026cb704e7b00a032a0c36 [file] [log] [blame]
<?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>January 12, 2007</announced>
<revised>January 12, 2007: 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 &quot;&gt;=www-client/w3m-0.5.1-r4&quot;</code>
</resolution>
<references>
<uri link="http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2006-6772">CVE-2006-6772</uri>
</references>
<metadata tag="submitter" timestamp="Thu, 11 Jan 2007 00:57:23 +0000">
aetius
</metadata>
<metadata tag="bugReady" timestamp="Thu, 11 Jan 2007 11:00:25 +0000">
DerCorny
</metadata>
</glsa>