blob: a16c7c5f763e8a5190e9d1d68b5cfd9bbee9594f [file] [log] [blame]
<?xml version="1.0" encoding="utf-8"?>
<glsa id="200904-11">
<title>Tor: Multiple vulnerabilities</title>
Multiple vulnerabilities in Tor might allow for heap corruption, Denial of
Service, escalation of privileges and information disclosure.
<product type="ebuild">tor</product>
<announced>April 08, 2009</announced>
<revised>April 08, 2009: 01</revised>
<package name="net-misc/tor" auto="yes" arch="*">
<unaffected range="ge"></unaffected>
<vulnerable range="lt"></vulnerable>
Tor is an implementation of second generation Onion Routing, a
connection-oriented anonymizing communication service.
Theo de Raadt reported that the application does not properly drop
privileges to the primary groups of the user specified via the "User"
configuration option (CVE-2008-5397).
rovv reported that the "ClientDNSRejectInternalAddresses" configuration
option is not always enforced (CVE-2008-5398).
Ilja van Sprundel reported a heap-corruption vulnerability that might
be remotely triggerable on some platforms (CVE-2009-0414).
It has been reported that incomplete IPv4 addresses are treated as
valid, violating the specification (CVE-2009-0939).
Three unspecified vulnerabilities have also been reported
(CVE-2009-0936, CVE-2009-0937, CVE-2009-0938).
<impact type="high">
A local attacker could escalate privileges by leveraging unintended
supplementary group memberships of the Tor process. A remote attacker
could exploit these vulnerabilities to cause a heap corruption with
unknown impact and attack vectors, to cause a Denial of Service via CPU
consuption or daemon crash, and to weaken anonymity provided by the
There is no known workaround at this time.
All Tor users should upgrade to the latest version:
# emerge --sync
# emerge --ask --oneshot --verbose &quot;&gt;=net-misc/tor-;</code>
<uri link="">CVE-2008-5397</uri>
<uri link="">CVE-2008-5398</uri>
<uri link="">CVE-2009-0414</uri>
<uri link="">CVE-2009-0936</uri>
<uri link="">CVE-2009-0937</uri>
<uri link="">CVE-2009-0938</uri>
<uri link="">CVE-2009-0939</uri>
<metadata tag="requester" timestamp="Sun, 25 Jan 2009 14:41:40 +0000">
<metadata tag="submitter" timestamp="Thu, 12 Feb 2009 16:48:01 +0000">
<metadata tag="bugReady" timestamp="Thu, 12 Feb 2009 16:48:17 +0000">