# CVE-2020-36468: Non-atomic writes in cgc

> Non-atomic pointer writes in the Rust cgc crate can lead to race conditions, potentially causing memory corruption or crashes.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Aug 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pwhf-7427-9vv2

## What is CVE-2020-36468?

CVE-2020-36468 is a medium-severity vulnerability in n/a, published on 8 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2020-36468?

2 open source packages ship an affected version, including cgc. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `cgc` | crates.io | All versions to 0.4.0 | None |
| `cgc` | crates.io | All versions to 0.4.0 | None |

Products: Cgc Project Cgc.

## How do I fix CVE-2020-36468?

No fix has been published for CVE-2020-36468 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-36468 being exploited?

There is no known exploitation of CVE-2020-36468 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-36466](https://insights.sbomify.com/CVE-2020-36466/): Data races in cgc (medium 5.9)
- [CVE-2020-36467](https://insights.sbomify.com/CVE-2020-36467/): Multiple soundness issues in cgc (medium 5.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-36468 and fix it if it is affected.

What it is: CVE-2020-36468 is a medium-severity vulnerability in n/a, published on 8 Aug 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-36468 in the wild and no public exploit code.

Affected packages and fixed versions:
- cgc (crates.io): affected all versions up to 0.4.0; no fix listed
- cgc (crates.io): affected all versions up to 0.4.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-36468/ (Markdown: https://insights.sbomify.com/CVE-2020-36468/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-36468
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-36468
- OSV: https://osv.dev/vulnerability/CVE-2020-36468

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-36468/
Summaries are generated and may contain mistakes; the official description above is the record.