CVE-2020-35877: An issue was discovered in the ozone crate through 2020-07-04 for Rust

Q: How do I fix CVE-2020-35877?

ozone: upgrade to newer than 0.1.0. Exact commands for each OS are on this page.

Q: Is CVE-2020-35877 being exploited?

CVE-2020-35877 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2020-35877 affect?

CVE-2020-35877 affects ozone. Severity is critical (CVSS 9.8). An issue was discovered in the ozone crate through 2020-07-04 for Rust. Memory safety is violated because of out-of-bounds access.

Q: How urgent is CVE-2020-35877?

Priority 58/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2020-35877 is a critical-severity flaw (CVSS 9.8) affecting ozone. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

An issue was discovered in the ozone crate through 2020-07-04 for Rust. Memory safety is violated because of out-of-bounds access.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.5% (top 25%)
CISA exploited list	No
Weakness	CWE-119
Published	2020-12-31
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: ozone project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2020-12-31 10:15 UTCPublished CVE record published
2026-06-17 03:14 UTCUpdated Record last modified

ozone project ozone UPGRADE

Affected: <= 0.1.0

Fixed in: newer than 0.1.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy ozone || rpm -q ozone || ozone --version

2. UPGRADE to newer than 0.1.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade ozone

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade ozone

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-35877?

ozone: upgrade to newer than 0.1.0. Exact commands for each OS are on this page.

Is CVE-2020-35877 being exploited?

CVE-2020-35877 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-35877 affect?

CVE-2020-35877 affects ozone. Severity is critical (CVSS 9.8). An issue was discovered in the ozone crate through 2020-07-04 for Rust. Memory safety is violated because of out-of-bounds access.

How urgent is CVE-2020-35877?

Priority 58/100. Critical severity; Remotely exploitable, no login, no user action

Related CVEs

CVE-2024-45106 HIGH 8.1 DOWNGRADE Improper authentication of an HTTP endpoint in the S3 Gateway of Apache Ozone 1.4.0 allows any authenticated K
CVE-2023-39196 MEDIUM 5.3 UPGRADE Improper Authentication vulnerability in Apache Ozone. The vulnerability allows an attacker to download metad
CVE-2021-41532 MEDIUM 5.3 UPGRADE In Apache Ozone before 1.2.0, Recon HTTP endpoints provide access to OM, SCM and Datanode metadata
CVE-2021-39236 HIGH 8.8 UPGRADE In Apache Ozone before 1.2.0, Authenticated users with valid Ozone S3 credentials can create specific OM reque
CVE-2021-39235 MEDIUM 6.5 UPGRADE In Apache Ozone before 1.2.0, Ozone Datanode doesn't check the access mode parameter of the block token

References

← Back to latest CVEs