{"id":"GHSA-w59h-378f-2frm","aliases":["RUSTSEC-2024-0005"],"status":"published","title":"Unsound sending of non-Send types across threads in threadalone","description":"Affected versions can run the `Drop` impl of a non-Send type on a different\nthread than it was created on.\n\nThe flaw occurs when a stderr write performed by the `threadalone` crate fails,\nfor example because stderr is redirected to a location on a filesystem that is\nfull, or because stderr is a pipe that has been closed by the reader.\n\nDropping a non-Send type on the wrong thread is unsound. If used with a type\nsuch as a pthread-based `MutexGuard`, [the consequence is undefined\nbehavior][mutexguard]. If used with `Rc`, there would be a data race on the\nreference count, which is likewise undefined behavior.\n\n[mutexguard]: https://github.com/rust-lang/rust/issues/23465#issuecomment-82730326","facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2024-01-07T12:00:00Z","modified":"2024-02-10T16:26:49Z","fixes":[{"ecosystem":"crates.io","package":"threadalone","fixed_in":["0.2.1"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"crates.io","package":"threadalone","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.2.1"}]}]},{"source":"osv","ecosystem":"crates.io","package":"threadalone","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"0.2.1"}]}]},{"source":"osv","ecosystem":"crates.io","package":"threadalone","ranges":[{"type":"SEMVER","events":[{"introduced":"0.0.0-0"},{"fixed":"0.2.1"}]}]}],"references":[{"url":"https://github.com/cr0sh/threadalone/issues/1","tags":["web","report"]},{"url":"https://rustsec.org/advisories/RUSTSEC-2024-0005.html","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-w59h-378f-2frm"},{"url":"https://crates.io/crates/threadalone","tags":["package"]}],"sources":{"ghsa":[{"id":"GHSA-w59h-378f-2frm","title":"Unsound sending of non-Send types across threads in threadalone","description":"Affected versions can run the `Drop` impl of a non-Send type on a different\nthread than it was created on.\n\nThe flaw occurs when a stderr write performed by the `threadalone` crate fails,\nfor example because stderr is redirected to a location on a filesystem that is\nfull, or because stderr is a pipe that has been closed by the reader.\n\nDropping a non-Send type on the wrong thread is unsound. If used with a type\nsuch as a pthread-based `MutexGuard`, [the consequence is undefined\nbehavior][mutexguard]. If used with `Rc`, there would be a data race on the\nreference count, which is likewise undefined behavior.\n\n[mutexguard]: https://github.com/rust-lang/rust/issues/23465#issuecomment-82730326\n\n","status":"published","published":"2024-01-23T14:43:35Z","modified":"2024-01-23T14:43:35Z","updated_at":"2026-11-02T14:37:32.302254Z"}],"osv":[{"id":"GHSA-w59h-378f-2frm","title":"Unsound sending of non-Send types across threads in threadalone","description":"Affected versions can run the `Drop` impl of a non-Send type on a different\nthread than it was created on.\n\nThe flaw occurs when a stderr write performed by the `threadalone` crate fails,\nfor example because stderr is redirected to a location on a filesystem that is\nfull, or because stderr is a pipe that has been closed by the reader.\n\nDropping a non-Send type on the wrong thread is unsound. If used with a type\nsuch as a pthread-based `MutexGuard`, [the consequence is undefined\nbehavior][mutexguard]. If used with `Rc`, there would be a data race on the\nreference count, which is likewise undefined behavior.\n\n[mutexguard]: https://github.com/rust-lang/rust/issues/23465#issuecomment-82730326\n\n","status":"published","published":"2024-01-23T14:43:35Z","modified":"2024-02-10T16:26:49.036729Z","updated_at":"2026-11-02T15:46:58.04805Z"},{"id":"RUSTSEC-2024-0005","title":"Unsound sending of non-Send types across threads","description":"Affected versions can run the `Drop` impl of a non-Send type on a different\nthread than it was created on.\n\nThe flaw occurs when a stderr write performed by the `threadalone` crate fails,\nfor example because stderr is redirected to a location on a filesystem that is\nfull, or because stderr is a pipe that has been closed by the reader.\n\nDropping a non-Send type on the wrong thread is unsound. If used with a type\nsuch as a pthread-based `MutexGuard`, [the consequence is undefined\nbehavior][mutexguard]. If used with `Rc`, there would be a data race on the\nreference count, which is likewise undefined behavior.\n\n[mutexguard]: https://github.com/rust-lang/rust/issues/23465#issuecomment-82730326","status":"published","published":"2024-01-07T12:00:00Z","modified":"2024-02-10T16:26:49.036729Z","updated_at":"2026-11-02T15:53:39.971022Z"}]}}