CVE-2012-5573
Last modified
CVE-2012-5573 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 3.15% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Torproject | Tor | <= 0.2.3.24 | Rc |
| Torproject | Tor | 0.0.2 | — |
| 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 | — |
Showing 50 of 84 affected configurations. See NVD for the full list.
References
- https://trac.torproject.org/projects/tor/ticket/6252Vendor Advisory
- https://trac.torproject.org/projects/tor/ticket/6252Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2012-5573?
How severe is CVE-2012-5573?
How do I fix CVE-2012-5573?
Are you affected by CVE-2012-5573?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
