CVE-2012-5573: Medium severity tor project tor vulnerability

Published Nov 26, 2012
·
Updated

It was reported [1],[2] that Tor suffered from a denial of service vulnerability due to an error when handling SENDME cells. This could be exploited to cause excessive consumption of memory resources within an entry node.

This is fixed in upstream version 0.2.3.25 (git [3]).

[1] https://secunia.com/advisories/51329/ [2] https://trac.torproject.org/projects/tor/ticket/6252 [3] https://gitweb.torproject.org/arma/tor.git/commitdiff/b9b54568c0bb64c32bd0b362954bdbc8c1234b16

Other sources

The connectionedgeprocessrelaycell 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 RELAYCOMMANDSENDME command.

MITRE

Affected Software

99 affected components
torproject Tor<=0.2.3.24
torproject Tor=0.0.2
torproject Tor=0.0.2-pre13
torproject Tor=0.0.2-pre14
torproject Tor=0.0.2-pre15
torproject Tor=0.0.2-pre16
torproject Tor=0.0.2-pre17
torproject Tor=0.0.2-pre18
torproject Tor=0.0.2-pre19
torproject Tor=0.0.2-pre20
torproject Tor=0.0.2-pre21
torproject Tor=0.0.2-pre22
torproject Tor=0.0.2-pre23
torproject Tor=0.0.2-pre24
torproject Tor=0.0.2-pre25
torproject Tor=0.0.2-pre26
torproject Tor=0.0.2-pre27
torproject Tor=0.0.3
torproject Tor=0.0.4
torproject Tor=0.0.5
torproject Tor=0.0.6
torproject Tor=0.0.6.1
torproject Tor=0.0.6.2
torproject Tor=0.0.7
torproject Tor=0.0.7.1
torproject Tor=0.0.7.2
torproject Tor=0.0.7.3
torproject Tor=0.0.8.1
torproject Tor=0.0.9.1
torproject Tor=0.0.9.2
torproject Tor=0.0.9.3
torproject Tor=0.0.9.4
torproject Tor=0.0.9.5
torproject Tor=0.0.9.6
torproject Tor=0.0.9.7
torproject Tor=0.0.9.8
torproject Tor=0.0.9.9
torproject Tor=0.0.9.10
torproject Tor=0.1.0.10
torproject Tor=0.1.0.11
torproject Tor=0.1.0.12
torproject Tor=0.1.0.13
torproject Tor=0.1.0.14
torproject Tor=0.1.0.15
torproject Tor=0.1.0.16
torproject Tor=0.1.0.17
torproject Tor=0.1.1.20
torproject Tor=0.1.1.21
torproject Tor=0.1.1.22
torproject Tor=0.1.1.23
torproject Tor=0.1.1.24
torproject Tor=0.1.1.25
torproject Tor=0.1.1.26
torproject Tor=0.1.2.13
torproject Tor=0.1.2.14
torproject Tor=0.1.2.15
torproject Tor=0.1.2.16
torproject Tor=0.1.2.17
torproject Tor=0.1.2.18
torproject Tor=0.1.2.19
torproject Tor=0.2.0.30
torproject Tor=0.2.0.31
torproject Tor=0.2.0.32
torproject Tor=0.2.0.33
torproject Tor=0.2.0.34
torproject Tor=0.2.0.35
torproject Tor=0.2.2.18
torproject Tor=0.2.2.19
torproject Tor=0.2.2.20
torproject Tor=0.2.2.21
torproject Tor=0.2.2.22
torproject Tor=0.2.2.23
torproject Tor=0.2.2.24
torproject Tor=0.2.2.25
torproject Tor=0.2.2.26
torproject Tor=0.2.2.27
torproject Tor=0.2.2.28
torproject Tor=0.2.2.29
torproject Tor=0.2.2.30
torproject Tor=0.2.2.31
torproject Tor=0.2.2.32
torproject Tor=0.2.2.33
torproject Tor=0.2.2.34
torproject Tor=0.2.2.35
torproject Tor=0.2.2.36
torproject Tor=0.2.2.37
torproject Tor=0.2.2.38
torproject Tor=0.2.3
torproject Tor=0.2.3.13-alpha
torproject Tor=0.2.3.14-alpha
torproject Tor=0.2.3.15-alpha
torproject Tor=0.2.3.16-alpha
torproject Tor=0.2.3.17-beta
torproject Tor=0.2.3.18-rc
torproject Tor=0.2.3.19-rc
torproject Tor=0.2.3.20-rc
torproject Tor=0.2.3.21-rc
torproject Tor=0.2.3.22-rc
torproject Tor=0.2.3.23-rc

Event History

Nov 26, 2012
Data Sourced
via Red Hat·04:41 PM
DescriptionSeverityAffected Software
Jan 1, 2013
CVE Published
via MITRE·11:00 AM
Data Sourced
via MITRE·11:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2012-5573?

CVE-2012-5573 has been classified as a denial of service vulnerability due to excessive memory consumption.

2

How do I fix CVE-2012-5573?

To mitigate CVE-2012-5573, upgrade to upstream version 0.2.3.25 or later of Tor.

3

What versions are affected by CVE-2012-5573?

CVE-2012-5573 affects various versions of Tor prior to 0.2.3.25, including several release candidates and earlier versions.

4

What type of attack can exploit CVE-2012-5573?

CVE-2012-5573 can be exploited by sending specially crafted SENDME cells to overwhelm an entry node's memory.

5

Is there a patch available for CVE-2012-5573?

Yes, a patch is included in the Tor release version 0.2.3.25 and later to address CVE-2012-5573.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203