From: Thierry Carrez <koon@gentoo.org>
To: gentoo-announce@lists.gentoo.org
Cc: bugtraq@securityfocus.com, full-disclosure@lists.grok.org.uk,
security-alerts@linuxsecurity.com
Subject: [gentoo-announce] [ GLSA 200506-18 ] Tor: Information disclosure
Date: Tue, 21 Jun 2005 22:12:31 +0200 [thread overview]
Message-ID: <42B874AF.9090601@gentoo.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2456 bytes --]
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Gentoo Linux Security Advisory GLSA 200506-18
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
http://security.gentoo.org/
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Severity: Low
Title: Tor: Information disclosure
Date: June 21, 2005
Bugs: #96320
ID: 200506-18
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Synopsis
========
A flaw in Tor may allow the disclosure of arbitrary memory portions.
Background
==========
Tor is an implementation of second generation Onion Routing, a
connection-oriented anonymizing communication service.
Affected packages
=================
-------------------------------------------------------------------
Package / Vulnerable / Unaffected
-------------------------------------------------------------------
1 net-misc/tor < 0.0.9.10 >= 0.0.9.10
Description
===========
A bug in Tor allows attackers to view arbitrary memory contents from an
exit server's process space.
Impact
======
A remote attacker could exploit the memory disclosure to gain sensitive
information and possibly even private keys.
Workaround
==========
There is no known workaround at this time.
Resolution
==========
All Tor users should upgrade to the latest available version:
# emerge --sync
# emerge --ask --oneshot --verbose ">=net-misc/tor-0.0.9.10"
References
==========
[ 1 ] Tor Security Announcement
http://archives.seul.org/or/announce/Jun-2005/msg00001.html
Availability
============
This GLSA and any updates to it are available for viewing at
the Gentoo Security Website:
http://security.gentoo.org/glsa/glsa-200506-18.xml
Concerns?
=========
Security is a primary focus of Gentoo Linux and ensuring the
confidentiality and security of our users machines is of utmost
importance to us. Any security concerns should be addressed to
security@gentoo.org or alternatively, you may file a bug at
http://bugs.gentoo.org.
License
=======
Copyright 2005 Gentoo Foundation, Inc; referenced text
belongs to its owner(s).
The contents of this document are licensed under the
Creative Commons - Attribution / Share Alike license.
http://creativecommons.org/licenses/by-sa/2.0
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
reply other threads:[~2005-06-21 20:27 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=42B874AF.9090601@gentoo.org \
--to=koon@gentoo.org \
--cc=bugtraq@securityfocus.com \
--cc=full-disclosure@lists.grok.org.uk \
--cc=gentoo-announce@lists.gentoo.org \
--cc=security-alerts@linuxsecurity.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox