CVE-2020-36468

mediumpriority · track · 24EPSS 0.010 · 62 %ileEUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
0.98% (62nd) EPSS
CVSS 4.3 · medium
Is it mine?
4 products
Check your exposure
Who says so?
4 sources
cnnvd · enisa_euvd · osv · nvd

EPSS · scored 2026-10-27

An issue was discovered in the cgc crate through 2020-12-10 for Rust. Ptr::write performs non-atomic write operations on an underlying pointer.

01

cvss

Technical severity, 0–10. One row per scoring source.

5.9
010

base score 0–10 · higher = more severe · hover a vector to decode

v2.04.3mediumAV:N/AC:M/Au:N/C:N/I:N/A:Pprimary · NVD / NIST USexploitability 8.6 · impact 2.9
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:Hprimary · NVD / NIST USexploitability 2.2 · impact 3.6
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondary · OSV
v3.15.4mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H/E:Usecondary · CVSS-BT (t0sche)
02

weaknesses

The CWE weakness classes this flaw belongs to.

03

affected products (4)

Products and version ranges known to be affected.

04

advisories (4)

Vendor and ecosystem advisories describing this.

  • GHSA-f3mq-99jr-ww4rMultiple soundness issues in cgc2021-08-25ghsa · osvUS

    Affected versions of this crate have the following issues: 1. `Ptr` implements `Send` and `Sync` for all types, this can lead to data races by sending non-thread safe types across threads. 2. `Ptr::get` violates mutable alias rules by returning multiple mutable references to the same object. 3. `Ptr::write` uses non-atomic writes to the underlying pointer. This means that when used across threads it can lead to data races.

  • GHSA-f9xr-3m55-5q2vData races in cgc2021-08-25ghsa · osvUS

    An issue was discovered in the cgc crate through 2020-12-10 for Rust. Ptr implements Send and Sync for all types

  • GHSA-pwhf-7427-9vv2Non-atomic writes in cgc2021-08-25ghsa · osvUS

    # Multiple soundness issues in `Ptr` in cgc Affected versions of this crate have the following issues: 1. `Ptr` implements `Send` and `Sync` for all types, this can lead to data races by sending non-thread safe types across threads. 2. `Ptr::get` violates mutable alias rules by returning multiple mutable references to the same object. 3. `Ptr::write` uses non-atomic writes to the underlying pointer. This means that when used across threads it can lead to data races.

  • RUSTSEC-2020-0148Multiple soundness issues in `Ptr`2020-12-10vendor · osvUS

    Affected versions of this crate have the following issues: 1. `Ptr` implements `Send` and `Sync` for all types, this can lead to data races by sending non-thread safe types across threads. 2. `Ptr::get` violates mutable alias rules by returning multiple mutable references to the same object. 3. `Ptr::write` uses non-atomic writes to the underlying pointer. This means that when used across threads it can lead to data races.

05

also known as (7)

Other names and identifiers for this entity.

06

sources

Which sources assert this record, and when.

published 2021-08-08modified 2026-06-17
07

references (6)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan