threadalone
Affected
- introduced
0.0.0-0, fixed0.2.1(semver)
Fixed versions
0.2.1
Fix
- Fixed version
0.2.1cargo update -p threadalone --precise 0.2.1
Advisory
Also known as: GHSA-w59h-378f-2frm
Unsound sending of non-Send types across threads
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][mutexguard]. If used with Rc, there would be a data race on the
reference count, which is likewise undefined behavior.
[mutexguard]: https://github.com/rust-lang/rust/issues/23465#issuecomment-82730326
Not rated by the source.
0.0.0-0, fixed 0.2.1 (semver)0.2.1
0.2.1cargo update -p threadalone --precise 0.2.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0