RUSTSEC-2020-0114

See a problem?
Please try reporting it to the source first.
Source
https://rustsec.org/advisories/RUSTSEC-2020-0114
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2020-0114.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2020-0114
Aliases
Published
2020-12-22T12:00:00Z
Modified
2023-11-08T04:03:42.275700Z
Severity
  • 5.9 (Medium) CVSS_V3 - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H CVSS Calculator
Summary
`Demuxer` can carry non-Send types across thread boundaries
Details

In the affected versions of this crate, Demuxer<T> 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<T>.

Database specific 
{
    "license": "CC0-1.0"
}
References

Affected packages

crates.io / va-ts

Package

Name
va-ts
View open source insights on deps.dev
Purl
pkg:cargo/va-ts

Affected ranges

Type
SEMVER
Events
Introduced
0.0.0-0
Fixed
0.0.4

Ecosystem specific 

{
    "affected_functions": null,
    "affects": {
        "os": [],
        "functions": [],
        "arch": []
    }
}

Database specific 

{
    "cvss": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
    "informational": null,
    "categories": [
        "memory-corruption",
        "thread-safety"
    ]
}