# CVE-2020-35878: Drop of uninitialized memory in Ozone

> Attackers can exploit uninitialized memory dropping in the ozone Rust crate to cause memory corruption, potentially leading to code execution or crashes.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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:** 31 Dec 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-m3ww-7hrp-gw9w

## What is CVE-2020-35878?

CVE-2020-35878 is a critical memory corruption vulnerability in n/a, published on 31 Dec 2020. 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 ozone crate through 2020-07-04 for Rust. Memory safety is violated because of the dropping of uninitialized memory.

Weakness: CWE-908 (Use of Uninitialized Resource), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ozone` | crates.io | All versions to 0.1.0 | None |
| `ozone` | crates.io | All versions to 0.1.0 | None |

Products: Ozone Project Ozone.

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

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

## Is CVE-2020-35878 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-35877](https://insights.sbomify.com/CVE-2020-35877/): Out of bounds read in Ozone (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-35878 is a critical memory corruption vulnerability in n/a, published on 31 Dec 2020. 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-35878 in the wild and no public exploit code.

Affected packages and fixed versions:
- ozone (crates.io): affected all versions up to 0.1.0; no fix listed
- ozone (crates.io): affected all versions up to 0.1.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-35878/ (Markdown: https://insights.sbomify.com/CVE-2020-35878/index.md)
```

## Sources

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

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