Tor up to 0.3.5.9/0.4.1.8/0.4.2.6 Padding circpad_setup_machine_on_circ memory leak
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Tor up to 0.3.5.9/0.4.1.8/0.4.2.6. Affected by this issue is the function circpad_setup_machine_on_circ of the component Padding Handler. The manipulation leads to memory leak.
This vulnerability is documented as CVE-2020-10593. The attack can be initiated remotely. There is not any exploit available.
You should upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in Tor up to 0.3.5.9/0.4.1.8/0.4.2.6 (Network Encryption Software). This issue affects the function circpad_setup_machine_on_circ of the component Padding Handler. The manipulation with an unknown input leads to a memory leak vulnerability. Using CWE to declare the problem leads to CWE-401. The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory. Impacted is availability. The summary by CVE is:
Tor before 0.3.5.10, 0.4.x before 0.4.1.9, and 0.4.2.x before 0.4.2.7 allows remote attackers to cause a Denial of Service (memory leak), aka TROVE-2020-004. This occurs in circpad_setup_machine_on_circ because a circuit-padding machine can be negotiated twice on the same circuit.
The weakness was released 03/23/2020. The identification of this vulnerability is CVE-2020-10593 since 03/15/2020. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 0.3.5.10, 0.4.1.9 or 0.4.2.7 eliminates this vulnerability.
Entry connected to this vulnerability is available at VDB-152020. If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 0.3.5.0
- 0.3.5.1
- 0.3.5.2
- 0.3.5.3
- 0.3.5.4
- 0.3.5.5
- 0.3.5.6
- 0.3.5.7
- 0.3.5.8
- 0.3.5.9
- 0.4.1.0
- 0.4.1.1
- 0.4.1.2
- 0.4.1.3
- 0.4.1.4
- 0.4.1.5
- 0.4.1.6
- 0.4.1.7
- 0.4.1.8
- 0.4.2.0
- 0.4.2.1
- 0.4.2.2
- 0.4.2.3
- 0.4.2.4
- 0.4.2.5
- 0.4.2.6
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.4VulDB Meta Temp Score: 6.3
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Memory leakCWE: CWE-401 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Tor 0.3.5.10/0.4.1.9/0.4.2.7
Timeline
03/15/2020 🔍03/23/2020 🔍
03/24/2020 🔍
04/30/2024 🔍
Sources
Advisory: 33619Status: Not defined
CVE: CVE-2020-10593 (🔍)
GCVE (CVE): GCVE-0-2020-10593
GCVE (VulDB): GCVE-100-152021
See also: 🔍
Entry
Created: 03/24/2020 08:13Updated: 04/30/2024 18:08
Changes: 03/24/2020 08:13 (38), 03/24/2020 08:18 (18), 04/30/2024 18:08 (19)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.