CVE-2020-36439

Description

An issue was discovered in the ticketed_lock crate before 0.3.0 for Rust. There are unconditional implementations of Send for ReadTicket<T> and WriteTicket<T>.

Category

8.1
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 0.34%
Third-Party Advisory githubusercontent.com Third-Party Advisory rustsec.org
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://rustsec.org/advisories/RUSTSEC-2020-0119.html third party advisory
https://raw.githubusercontent.com/rustsec/advisory-db/main/crates/ticketed_lock/RUSTSEC-2020-0119.md third party advisory

Frequently Asked Questions

What is the severity of CVE-2020-36439?
CVE-2020-36439 has been scored as a high severity vulnerability.
How to fix CVE-2020-36439?
To fix CVE-2020-36439, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2020-36439 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2020-36439 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.