VDB-11708 · Ticket #7889 · OSVDB 101622

Tor 0.2.4.9-alpha Crafted Create/Relay Cell relay_lookup_conn denial of service

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
6.2$0-$5k0.00

Summaryinfo

A vulnerability was found in Tor 0.2.4.9-alpha and classified as problematic. This issue affects the function relay_lookup_conn of the component Crafted Create/Relay Cell Handler. Such manipulation of the argument RELAY_COMMAND_BEGIN/RELAY_COMMAND_BEGIN_DIR/RELAY_COMMAND_RESOLVE leads to denial of service. There is no available exploit. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability was found in Tor 0.2.4.9-alpha (Network Encryption Software). It has been rated as critical. Affected by this issue is the function relay_lookup_conn of the component Crafted Create/Relay Cell Handler. The manipulation of the argument RELAY_COMMAND_BEGIN/RELAY_COMMAND_BEGIN_DIR/RELAY_COMMAND_RESOLVE with an unknown input leads to a denial of service vulnerability. Using CWE to declare the problem leads to CWE-404. The product does not release or incorrectly releases a resource before it is made available for re-use. Impacted is availability.

The weakness was presented 01/08/2013 by oftc_must_be_destroyed as Ticket #7889 as not defined bug report (Website). The advisory is shared for download at trac.torproject.org. The attack may be launched remotely. There are known technical details, but no exploit is available. The following code is the reason for this vulnerability: 

if (test_stream_id == 0)
    goto again;

Upgrading to version 0.2.4.10-alpha eliminates this vulnerability. A possible mitigation has been published 4 weeks after the disclosure of the vulnerability.

The vulnerability is also documented in the vulnerability database at OSVDB (101622†). See VDB-11707 for similar entry. Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 6.2

VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

Exploitinginfo

Class: Denial of service
CWE: CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Upgrade: Tor 0.2.4.10-alpha

Timelineinfo

01/08/2013 🔍
02/04/2013 +27 days 🔍
01/03/2014 +333 days 🔍
03/24/2019 +1906 days 🔍

Sourcesinfo

Advisory: Ticket #7889
Researcher: oftc_must_be_destroyed
Status: Not defined

GCVE (VulDB): GCVE-100-11708
OSVDB: 101622

See also: 🔍

Entryinfo

Created: 01/03/2014 16:58
Updated: 03/24/2019 09:23
Changes: 01/03/2014 16:58 (48), 03/24/2019 09:23 (2)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!