The compare_tor_addr_to_addr_policy function in or/policies.c in Tor before 0.2.2.39, and 0.2.3.x before 0.2.3.21-rc, allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a zero-valued port field that is not properly handled during policy comparison.

- update to 0.2.2.39 [bnc#780620] Changes in version     0.2.2.39 - 2012-09-11 Tor 0.2.2.39 fixes two more     opportunities for remotely triggerable assertions. o     Security fixes :

  - Fix an assertion failure in tor_timegm() that could be     triggered by a badly formatted directory object     (CVE-2012-4922).

  - Do not crash when comparing an address with port value 0     to an address policy. This bug could have been used to     cause a remote assertion failure by or against directory     authorities, or to allow some applications to crash     clients (CVE-2012-4419).

Updated tor package fixes security vulnerabilities :

Tor before 0.2.2.34, when configured as a client or bridge, sends a TLS certificate chain as part of an outgoing OR connection, which allows remote relays to bypass intended anonymity properties by reading this chain and then determining the set of entry guards that the client or bridge had selected (CVE-2011-2768).

Tor before 0.2.2.34, when configured as a bridge, accepts the CREATE and CREATE_FAST values in the Command field of a cell within an OR connection that it initiated, which allows remote relays to enumerate bridges by using these values (CVE-2011-2769).

Use-after-free vulnerability in dns.c in Tor before 0.2.2.38 might allow remote attackers to cause a denial of service (daemon crash) via vectors related to failed DNS requests (CVE-2012-3517).

The networkstatus_parse_vote_from_string function in routerparse.c in Tor before 0.2.2.38 does not properly handle an invalid flavor name, which allows remote attackers to cause a denial of service (out-of-bounds read and daemon crash) via a crafted (1) vote document or (2) consensus document (CVE-2012-3518).

routerlist.c in Tor before 0.2.2.38 uses a different amount of time for relay-list iteration depending on which relay is chosen, which might allow remote attackers to obtain sensitive information about relay selection via a timing side-channel attack (CVE-2012-3519).

The compare_tor_addr_to_addr_policy function in or/policies.c in Tor before 0.2.2.39, and 0.2.3.x before 0.2.3.21-rc, allows remote attackers to cause a denial of service (assertion failure and daemon exit) via a zero-valued port field that is not properly handled during policy comparison (CVE-2012-4419).

Tor before 0.2.2.39, when waiting for a client to renegotiate, allowed it to add bytes to the input buffer, allowing a crash to be caused remotely (tor-5934, tor-6007).

Denial of Service vulnerability in Tor before 0.2.3.25, due to an error when handling SENDME cells and can be exploited to cause excessive consumption of memory resources within an entry node (SA51329, CVE-2012-5573).

The version of Tor shipped in MBS1 did not have correctly formed systemd unit and thus failed to start.

This updated version corrects this problem and restores working behaviour.

. .

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote host is affected by the vulnerability described in GLSA-201301-03 (Tor: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in Tor. Please review the       CVE identifiers referenced below for details.
  Impact :

    A remote attacker could cause a Denial of Service condition or obtain       sensitive information.
  Workaround :

    There is no known workaround at this time.

. . .

Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Several vulnerabilities have been discovered in Tor, an online privacy tool.

  - CVE-2012-3518     Avoid an uninitialised memory read when reading a vote     or consensus document that has an unrecognized flavour     name. This could lead to a remote crash, resulting in     denial of service.

  - CVE-2012-3519     Try to leak less information about what relays a client     is choosing to a side-channel attacker.

  - CVE-2012-4419     By providing specially crafted date strings to a victim     tor instance, an attacker can cause it to run into an     assertion and shut down.

Additionally the update to stable includes the following fixes: when waiting for a client to renegotiate, don't allow it to add any bytes to the input buffer. This fixes a potential DoS issue [ tor-5934, tor-6007].

ID	Name	Product	Family	Severity
74768	openSUSE Security Update : tor (openSUSE-SU-2012:1278-1)	Nessus	SuSE Local Security Checks	medium
66144	Mandriva Linux Security Advisory : tor (MDVSA-2013:132)	Nessus	Mandriva Local Security Checks	medium
64440	Fedora 17 : tor-0.2.2.39-1700.fc17 (2012-14650)	Nessus	Fedora Local Security Checks	medium
63437	GLSA-201301-03 : Tor: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	medium
62234	Fedora 18 : tor-0.2.2.39-1800.fc18 (2012-14638)	Nessus	Fedora Local Security Checks	medium
62086	Debian DSA-2548-1 : tor - several vulnerabilities	Nessus	Debian Local Security Checks	medium

Detections

Analytics

CVE-2012-4419

high

Tenable Plugins

medium

medium

medium

medium

medium

medium