Skip to content
Fencer Intel
medium —

GHSA-rwf4-gx62-rqfw json

`MsQueue` `push`/`pop` use the wrong orderings

published 4y ago modified 3y ago also RUSTSEC-2022-0029

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

Affected versions of this crate use orderings which are too weak to support this data structure. It is likely this has caused memory corruption in the wild: <https://github.com/crossbeam-rs/crossbeam/issues/97#issuecomment-412785919>.

Patch / fix

  • crates.io crossbeam 0.3.0

Is GHSA-rwf4-gx62-rqfw in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
crates.io crossbeam
<0.3.0
>=0.0.0-0, <0.3.0
0.3.0

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.