The connection_edge_process_relay_cell function in or/relay.c in Tor before 0.2.3.25 maintains circuits even if an unexpected SENDME cell arrives, which might allow remote attackers to cause a denial of service (memory consumption or excessive cell reception rate) or bypass intended flow-control restrictions via a RELAY_COMMAND_SENDME command.

- Tear down the circuit when receiving an unexpected     SENDME cell. Prevents circumvention of the network's     flow control, exhaustion of network resources and     possible denial-of-service attacks on entry nodes     [bnc#791374] CVE-2012-5573, adding     tor-0.2.2.39-SENDME-DOS.patch

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.

Significant package cleanup, including :

  - remove dependency on fedora-usermgmt

    - merge tor-core, tor-systemd and torify into previously       empty tor package

    - remove unnecessary /var/run/tor

    - disallow group read for /var/log/tor

    - use --defaults-torrc as recommended by upstream

    - increase LimitNOFILE in tor.service from 4096 to 32768

    - torify subpackage should depend on torsocks not tsocks       (#908569) Fix outstanding security issues, plus       package cleanup torify subpackage should depend on       torsocks not tsocks

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.

Update for security and massive revamp of spec Fix outstanding security issues, plus package cleanup torify subpackage should depend on torsocks not tsocks

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.

ID	Name	Product	Family	Severity
74828	openSUSE Security Update : tor (openSUSE-SU-2012:1624-1)	Nessus	SuSE Local Security Checks	medium
66144	Mandriva Linux Security Advisory : tor (MDVSA-2013:132)	Nessus	Mandriva Local Security Checks	medium
65671	Fedora 17 : tor-0.2.3.25-1702.fc17 (2013-3773)	Nessus	Fedora Local Security Checks	medium
65591	Fedora 18 : tor-0.2.3.25-1802.fc18 (2013-3434)	Nessus	Fedora Local Security Checks	medium
63437	GLSA-201301-03 : Tor: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	medium

Detections

Analytics

CVE-2012-5573

high

Tenable Plugins

medium

medium

medium

medium

medium