VulertSecurity VulertSecurity

Vulnerability Database · crates.io · Package report

ozone: vulnerability history, versions and safety

ozone is a package in the crates.io ecosystem. Vulert records 4 vulnerabilities for it across 2 releases, from Jul 2020 to Aug 2021. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C2 U2
i
4 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all ozone vulnerabilities

Vulert verdict on ozone 0.1.0 i

Updated on 23 Oct 2026

Careful: 0.1.0 has 4 known vulnerabilities, and 4 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 39/100
  • Security Some issues to review
  • Maintenance Slowing
  • Popularity Little adoption
  • Community Inactive

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 0.1.0 — affected i
  • Vulnerabilities on record 4 over 1 year · 0 in the last year i
  • Latest disclosure 25 Aug 2021 i
  • Highest CVSS 9.8 i
  • With no published fix 4 i
  • Stars 5 i
  • OpenSSF scorecard 1/10 i
  • Last release 109 months ago i
  • Licence MPL-2.0 i

Version list, release dates, licence and dependants published by crates.io, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for ozone, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.1.0 22 Sep 2017 C2 U2 MPL-2.0 No Details →
0.0.1 23 Jun 2015 C2 U2 — No Details →

All 2 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 2
  • 2021 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for ozone

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2020-35878: Ozone - Drop of uninitialized memory 9.8 critical No fix published 25 Aug 2021
CVE-2020-35877: Out of Bounds Read in Ozone 9.8 critical No fix published 04 Jul 2020
CVE-2020-35877: Memory Safety Issues in Ozone 9.8 critical No fix published 04 Jul 2020
CVE-2020-35877: Out of Bounds Read in Ozone 9.8 critical No fix published 25 Aug 2021

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About ozone

Is ozone safe to use?

Vulert records 4 vulnerabilities for ozone in crates.io: 2 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is ozone's Vulert package health score?

Vulert scores ozone 39/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of ozone affected?

Yes. 0.1.0, the version you would install today, has 4 known vulnerabilities, and 4 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does ozone have?

4 vulnerabilities are recorded for ozone in the crates.io ecosystem: 2 critical, 0 high, 0 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new ozone vulnerabilities disclosed?

0 vulnerabilities were recorded for ozone in the last 12 months, and the oldest entry in this database dates to 04 Jul 2020. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of ozone are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor ozone for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the ozone version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.