How severe is CVE-2020-36217?

CVE-2020-36217 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.

Is CVE-2020-36217 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (62nd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2020-36217?

CVE-2020-36217 affects May Queue Project May Queue. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2020-36217?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2020-36217 published?

CVE-2020-36217 was published on 2021-01-26 and last updated on 2026-06-17.

CVE-2020-36217

CVE-2020-36217 is a medium-severity vulnerability in May Queue Project May Queue with a CVSS 3.x base score of 5.9. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-662.

Key facts

Severity: Medium (CVSS 3.x base score 5.9)
CVSS v2: 4.3
EPSS exploit prediction: 1% (62nd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-662
Affected product: May Queue Project May Queue
Published: 2021-01-26
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2020-36217?: 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.
How severe is CVE-2020-36217?: CVE-2020-36217 has a CVSS 3.x base score of 5.9, rated medium severity. It is exploitable over network with high attack complexity, requires no privileges and no user interaction. Impact on confidentiality is none, integrity none, and availability high.
Is CVE-2020-36217 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (62nd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2020-36217?: CVE-2020-36217 affects May Queue Project May Queue. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2020-36217?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2020-36217 published?: CVE-2020-36217 was published on 2021-01-26 and last updated on 2026-06-17.

References

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

Affected products (1)

cpe:2.3:a:may_queue_project:may_queue:*:*:*:*:*:rust:*:*

Other CWE-662 vulnerabilities

CVE-2018-15555 — Critical (CVSS 9.8): On Telus Actiontec WEB6000Q v1.1.02.22 devices, an attacker can login with root level access with the user "root" and…
CVE-2024-32644 — Critical (CVSS 9.1): Evmos is a scalable, high-throughput Proof-of-Stake EVM blockchain that is fully compatible and interoperable with…
CVE-2026-53277 — High (CVSS 8.8): In the Linux kernel, the following vulnerability has been resolved: KVM: arm64: Take the SRCU lock for page table…
CVE-2022-23005 — High (CVSS 8.7): Western Digital has identified a weakness in the UFS standard that could result in a security vulnerability. This…
CVE-2016-8368 — High (CVSS 8.6): An issue was discovered in Mitsubishi Electric Automation MELSEC-Q series Ethernet interface modules QJ71E71-100, all…
CVE-2022-1931 — High (CVSS 8.1): Incorrect Synchronization in GitHub repository polonel/trudesk prior to 1.2.3.

Browse all CWE-662 vulnerabilities →