futures-util Crate up to 0.3.6 on Rust MutexGuard::map race condition
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 0.00 |
Summary
A vulnerability was found in futures-util Crate up to 0.3.6 on Rust. It has been classified as problematic. This vulnerability affects the function MutexGuard::map. This manipulation causes race condition.
This vulnerability is tracked as CVE-2020-35905. No exploit exists.
Upgrading the affected component is recommended.
Details
A vulnerability was found in futures-util Crate up to 0.3.6 on Rust (Rust Package). It has been declared as problematic. Affected by this vulnerability is the function MutexGuard::map. The manipulation with an unknown input leads to a race condition vulnerability. The CWE definition for the vulnerability is CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently. The impact remains unknown.
The weakness was disclosed 12/31/2020 as RUSTSEC-2020-0059. The advisory is shared at rustsec.org. This vulnerability is known as CVE-2020-35905. Technical details are known, but no exploit is available.
Upgrading to version 0.3.7 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.5VulDB Meta Temp Score: 5.3
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
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: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
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: futures-util Crate 0.3.7
Timeline
12/31/2020 🔍12/31/2020 🔍
12/31/2020 🔍
Sources
Advisory: RUSTSEC-2020-0059Status: Confirmed
CVE: CVE-2020-35905 (🔍)
GCVE (CVE): GCVE-0-2020-35905
GCVE (VulDB): GCVE-100-167137
Entry
Created: 12/31/2020 15:10Changes: 12/31/2020 15:10 (39)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.