Skip to content

Data races in bunch

High severity GitHub Reviewed Published Aug 25, 2021 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

cargo bunch (Rust)

Affected versions

<= 0.1.0

Patched versions

None

Description

An issue was discovered in the bunch crate through 2020-11-12 for Rust.
Affected versions of this crate unconditionally implements Send/Sync for Bunch<T>.
This allows users to insert T: !Sync to Bunch<T>. It is possible to create a data race to a T: !Sync by invoking the Bunch::get() API (which returns &T) from multiple threads. It is also possible to send T: !Send to other threads by inserting T inside Bunch<T> and sending Bunch<T> to another thread, allowing to create a data race by inserting types like T = Rc<_>.

Such data races can lead to memory corruption.

References

Published by the National Vulnerability Database Aug 8, 2021
Reviewed Aug 9, 2021
Published to the GitHub Advisory Database Aug 25, 2021
Last updated Feb 1, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.455%
(75th percentile)

Weaknesses

CVE ID

CVE-2020-36450

GHSA ID

GHSA-jwph-qp5h-f9wj

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.