# GHSA-rwf4-gx62-rqfw: `MsQueue` `push`/`pop` use the wrong orderings > Weak memory orderings in MsQueue push/pop operations can lead to memory corruption, potentially allowing code execution or crashes. - **Severity:** Not scored - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Not stated - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 7 Jun 2022 - **Also known as:** RUSTSEC-2022-0029 ## What is GHSA-rwf4-gx62-rqfw? GHSA-rwf4-gx62-rqfw is a memory corruption vulnerability in crossbeam, published on 7 Jun 2022. ### Official description 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: . ## Which versions are affected by GHSA-rwf4-gx62-rqfw? 3 open source packages ship an affected version, including crossbeam. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `crossbeam` | crates.io | All versions | 0.3.0 | | `crossbeam` | crates.io | All versions | 0.3.0 | | `crossbeam` | crates.io | From 0.0.0-0 | 0.3.0 | ## How do I fix GHSA-rwf4-gx62-rqfw? Upgrade crossbeam to 0.3.0 or later. ## Is GHSA-rwf4-gx62-rqfw being exploited? There is no known exploitation of GHSA-rwf4-gx62-rqfw in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-rwf4-gx62-rqfw and fix it if it is affected. What it is: GHSA-rwf4-gx62-rqfw is a memory corruption vulnerability in crossbeam, published on 7 Jun 2022. Exploitation: There is no known exploitation of GHSA-rwf4-gx62-rqfw in the wild and no public exploit code. Affected packages and fixed versions: - crossbeam (crates.io): affected all versions; fixed in 0.3.0 - crossbeam (crates.io): affected all versions; fixed in 0.3.0 - crossbeam (crates.io): affected from 0.0.0-0; fixed in 0.3.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/GHSA-rwf4-gx62-rqfw/ (Markdown: https://insights.sbomify.com/GHSA-rwf4-gx62-rqfw/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-rwf4-gx62-rqfw --- From sbomify Insights: https://insights.sbomify.com/GHSA-rwf4-gx62-rqfw/ Summaries are generated and may contain mistakes; the official description above is the record.