GHSA-3HJ2-HH36-HV9V
Vulnerability from github – Published: 2021-08-25 20:51 – Updated: 2023-06-13 22:11
VLAI?
Summary
Data race in va-ts
Details
In the affected versions of this crate, Demuxer unconditionally implemented Send with no trait bounds on T. This allows sending a non-Send type T across thread boundaries, which can cause undefined behavior like unlocking a mutex from a thread that didn't lock the mutex, or memory corruption from data race. The flaw was corrected in commit 0562cbf by adding a T: Send bound to the Send impl for Demuxer.
Severity ?
5.9 (Medium)
{
"affected": [
{
"package": {
"ecosystem": "crates.io",
"name": "va-ts"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "0.0.4"
}
],
"type": "ECOSYSTEM"
}
]
}
],
"aliases": [
"CVE-2020-36220"
],
"database_specific": {
"cwe_ids": [
"CWE-662",
"CWE-667",
"CWE-787"
],
"github_reviewed": true,
"github_reviewed_at": "2021-08-19T18:47:06Z",
"nvd_published_at": null,
"severity": "MODERATE"
},
"details": "In the affected versions of this crate, Demuxer\u003cT\u003e unconditionally implemented Send with no trait bounds on T. This allows sending a non-Send type T across thread boundaries, which can cause undefined behavior like unlocking a mutex from a thread that didn\u0027t lock the mutex, or memory corruption from data race. The flaw was corrected in commit `0562cbf` by adding a T: Send bound to the Send impl for Demuxer\u003cT\u003e.",
"id": "GHSA-3hj2-hh36-hv9v",
"modified": "2023-06-13T22:11:43Z",
"published": "2021-08-25T20:51:56Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2020-36220"
},
{
"type": "WEB",
"url": "https://github.com/video-audio/va-ts/issues/4"
},
{
"type": "PACKAGE",
"url": "https://github.com/video-audio/va-ts"
},
{
"type": "WEB",
"url": "https://rustsec.org/advisories/RUSTSEC-2020-0114.html"
}
],
"schema_version": "1.4.0",
"severity": [
{
"score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
"type": "CVSS_V3"
}
],
"summary": "Data race in va-ts"
}
Loading…
Loading…
Sightings
| Author | Source | Type | Date |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…