How severe is GHSA-w59h-378f-2frm?

No CVSS score has been assigned to GHSA-w59h-378f-2frm yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-w59h-378f-2frm?

GHSA-w59h-378f-2frm affects the following packages: threadalone (crates.io). Ecosystems affected: crates.io.

How do I fix GHSA-w59h-378f-2frm?

Update threadalone to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w59h-378f-2frm is resolved across your whole dependency graph.

How do I detect GHSA-w59h-378f-2frm in my crates.io dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for threadalone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-w59h-378f-2frm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-w59h-378f-2frm?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w59h-378f-2frm can be triaged on real exposure rather than presence alone.

Is GHSA-w59h-378f-2frm actively exploited in the wild?

No public exploit code has been indexed for GHSA-w59h-378f-2frm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-w59h-378f-2frm published, and has it been updated?

GHSA-w59h-378f-2frm was published on January 23, 2024 and was last updated on February 10, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

GHSA-w59h-378f-2frm — threadalone

GHSA-w59h-378f-2frm is a security vulnerability in threadalone. A fix is available for threadalone — see the affected versions and patch details below.

Unsound sending of non-Send types across threads in threadalone

Also known asRUSTSEC-2024-0005

Published

Jan 23, 2024

Updated

Feb 10, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Feb 10, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🦀threadalone

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`threadalone`	all versions	0.2.1`cargo update -p threadalone --precise 0.2.1`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for threadalone, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update threadalone to 0.2.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w59h-378f-2frm is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-w59h-378f-2frm can be triaged on real exposure rather than presence alone.

Tailored to GHSA-w59h-378f-2frm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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 undefi

O3 Security · Impact-Aware SCA

Is GHSA-w59h-378f-2frm in your dependencies?

O3 Security finds GHSA-w59h-378f-2frm across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works