CVE-2020-36208
HIGHCVSS 7.8/10EPSS 0.43%
Last modified
CVE-2020-36208 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. An issue was discovered in the conquer-once crate before 0.3.2 for Rust. Thread crossing can occur for a non-Send but Sync type, leading to memory corruption.. EPSS estimates a 0.43% chance of exploitation in the next 30 days.
Description
An issue was discovered in the conquer-once crate before 0.3.2 for Rust. Thread crossing can occur for a non-Send but Sync type, leading to memory corruption.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Conquer-Once Project | Conquer-Once | < 0.3.2 |
References
- https://rustsec.org/advisories/RUSTSEC-2020-0101.htmlExploit, Vendor Advisory
- https://rustsec.org/advisories/RUSTSEC-2020-0101.htmlExploit, Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2020-36208?
An issue was discovered in the conquer-once crate before 0.3.2 for Rust. Thread crossing can occur for a non-Send but Sync type, leading to memory corruption.
How severe is CVE-2020-36208?
CVE-2020-36208 has a CVSS score of 7.8/10 (HIGH severity). The EPSS model estimates a 0.43% probability of exploitation in the next 30 days.
How do I fix CVE-2020-36208?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2020
- CVE-2020-36202An issue was discovered in the async-h1 crate before 2.3.0 f…6.1
- CVE-2020-36203An issue was discovered in the reffers crate through 2020-12…4.7
- CVE-2020-36204An issue was discovered in the im crate through 2020-11-09 f…4.7
- CVE-2020-36205An issue was discovered in the xcb crate through 2020-12-10 …5.5
- CVE-2020-36206An issue was discovered in the rusb crate before 0.7.0 for R…7
- CVE-2020-36207An issue was discovered in the aovec crate through 2020-12-1…7
- CVE-2020-36209An issue was discovered in the late-static crate before 0.4.…7
- CVE-2020-3621u'Lack of check to ensure that the TX read index & RX write …5.5
- CVE-2020-36210An issue was discovered in the autorand crate before 0.2.3 f…7.8
- CVE-2020-36211An issue was discovered in the gfwx crate before 0.3.0 for R…7
- CVE-2020-36212An issue was discovered in the abi_stable crate before 0.9.1…7.5
- CVE-2020-36213An issue was discovered in the abi_stable crate before 0.9.1…7.5
Are you affected by CVE-2020-36208?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST