Vulnerability Database · crates.io · slice-ring-buffer · Version
slice-ring-buffer 0.3.4
0.3.4 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 0.3.4.
Critical 0 High 0 Medium 0 Low 0 Unrated 1
-
Released 27 Jul 2024
Status latest release
Licence Apache-2.0 OR MIT
Also known from other sources 2
Newer releases 4
Database updated 23/Oct/2026
Release and licence data published by crates.io. 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 Vulnerabilities affecting this version
slice-ring-buffer 0.3.4 vulnerabilities
1 vulnerability cover slice-ring-buffer 0.3.4. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| Critical Memory Corruption Vulnerabilities in slice-ring-buffer Package | N/A unrated | No fix published | 16 Jun 2025 |
Looking for another version, or everything Vulert holds for slice-ring-buffer?
Questions
About slice-ring-buffer 0.3.4
Is slice-ring-buffer 0.3.4 vulnerable?
Yes. 1 vulnerability in the Vulert database cover slice-ring-buffer 0.3.4: 0 critical, 0 high, 0 medium and 0 low, plus 1 not yet rated. The upgrade Vulert recommends is 0.3.4, and each entry above names the fixed version to move to.
Which version of slice-ring-buffer should I use instead of 0.3.4?
0.3.4 is the version Vulert recommends for this release line, which is also the release the publisher currently ships. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 0.3.4 the latest release of slice-ring-buffer?
Yes. 0.3.4 is the current release, published 27 Jul 2024. Staying on the current line is what keeps you inside the publisher's fixes.
How do I monitor slice-ring-buffer for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the slice-ring-buffer version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.