RUSTSEC-2024-0005

See a problem?
Please try reporting it to the source first.
Source
https://rustsec.org/advisories/RUSTSEC-2024-0005
Import Source
https://github.com/rustsec/advisory-db/blob/osv/crates/RUSTSEC-2024-0005.json
JSON Data
https://api.osv.dev/v1/vulns/RUSTSEC-2024-0005
Aliases
Published
2024-01-07T12:00:00Z
Modified
2024-02-10T16:26:49.036729Z
Summary
Unsound sending of non-Send types across threads
Details

Affected versions can run the Drop impl of a non-Send type on a different thread than it was created on.

The flaw occurs when a stderr write performed by the threadalone crate fails, for example because stderr is redirected to a location on a filesystem that is full, or because stderr is a pipe that has been closed by the reader.

Dropping a non-Send type on the wrong thread is unsound. If used with a type such as a pthread-based MutexGuard, the consequence is undefined behavior. If used with Rc, there would be a data race on the reference count, which is likewise undefined behavior.

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

Affected packages

crates.io / threadalone

Package

Name
threadalone
View open source insights on deps.dev
Purl
pkg:cargo/threadalone

Affected ranges

Type
SEMVER
Events
Introduced
0.0.0-0
Fixed
0.2.1

Ecosystem specific 

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

Database specific

cvss

null

informational

"unsound"

categories

[]