blob: 0bd1787b29ee5301a156530aca484a3bc2027c4b [file] [log] [blame]
<?xml version="1.0" encoding="UTF-8"?>
<glsa id="201201-12">
<title>Tor: Multiple vulnerabilities</title>
<synopsis>Multiple vulnerabilities have been found in Tor, the most severe of
which may allow a remote attacker to execute arbitrary code.
<product type="ebuild">Tor</product>
<announced>January 23, 2012</announced>
<revised>January 23, 2012: 1</revised>
<package name="net-misc/tor" auto="yes" arch="*">
<unaffected range="ge"></unaffected>
<vulnerable range="lt"></vulnerable>
<p>Tor is an implementation of second generation Onion Routing, a
connection-oriented anonymizing communication service.
<p>Multiple vulnerabilities have been discovered in Tor:</p>
<li>When configured as client or bridge, Tor uses the same TLS
certificate chain for all outgoing connections (CVE-2011-2768).
<li>When configured as a bridge, Tor relays can distinguish incoming
bridge connections from client connections (CVE-2011-2769).
<li>An error in or/buffers.c could result in a heap-based buffer overflow
<impact type="normal">
<p>A remote attacker could possibly execute arbitrary code or cause a
Denial of Service. Furthermore, a remote relay the user is directly
connected to may be able to disclose anonymous information about that
user or enumerate bridges in the user's connection.
<p>There is no known workaround at this time.</p>
<p>All Tor users should upgrade to the latest version:</p>
# emerge --sync
# emerge --ask --oneshot --verbose "&gt;=net-misc/tor-"
<uri link="">CVE-2011-2768</uri>
<uri link="">CVE-2011-2769</uri>
<uri link="">CVE-2011-2778</uri>
<metadata timestamp="Sun, 01 Jan 2012 17:49:33 +0000" tag="requester">
<metadata timestamp="Mon, 23 Jan 2012 19:55:45 +0000" tag="submitter">ackle</metadata>