Lucene search
K

RUSTSEC-2020-0113 AtomicOption should have Send + Sync bound on its type argument.

🗓️ 31 Oct 2020 12:00:00Reported by GoogleType 
osv
 osv
🔗 osv.dev👁 13 Views

AtomicOption type should have Send + Sync bound on its type argument. Affected versions unconditionally implement Sync, allowing non-Sync types to be moved across thread boundaries and non-Send types to be sent to other threads, leading to data races and undefined behavior

Related
Refs
ReporterTitlePublishedViews
Family
CNNVD
Rust Security Vulnerabilities
26 Jan 202100:00
cnnvd
CVE
CVE-2020-36219
22 Jan 202109:04
cve
Cvelist
CVE-2020-36219
22 Jan 202109:04
cvelist
EUVD
EUVD-2021-1638
7 Oct 202500:30
euvd
Github Security Blog
Data race in atomic-option
25 Aug 202120:51
github
NVD
CVE-2020-36219
26 Jan 202118:15
nvd
OSV
CVE-2020-36219
26 Jan 202118:15
osv
OSV
GHSA-8GF5-Q9P9-WVMC Data race in atomic-option
25 Aug 202120:51
osv
Prion
Design/Logic Flaw
26 Jan 202118:15
prion
RedhatCVE
CVE-2020-36219
22 May 202515:33
redhatcve
Rows per page

Data

Build on a solid foundation with Vulners data

We provide the essential building blocks for cybersecurity solutions with comprehensive, structured, and constantly updated vulnerability and exploits data

Api

Power your application with Vulners API

The Vulners REST API offers reliable, high-performance access to vulnerability intelligence, with 99.9% SLA uptime and CDN-backed data delivery for seamless global access

App

Assess and manage vulnerabilities with Vulners tools

Built on top of Vulners' database and SDK, end-user solutions give security professionals and developers lightweight and powerful tools for vulnerability remediation

08 Nov 2023 04:03Current
5.6Medium risk
Vulners AI Score5.6
CVSS 3.15.9
EPSS0.01107
13