Metrics UtilApplication · Metrics Util Project
CVE-2021-45704
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn issue was discovered in the metrics-util crate before 0.7.0 for Rust. There is a data race and memory corruption because AtomicBucket<T> unconditionally implements the Send and Sync traits.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe metrics-util crate before v0.7.0 has a concurrency vulnerability where AtomicBucket<T> unconditionally implements the Send and Sync traits. This allows the type to be shared across thread boundaries without proper synchronization, leading to undefined behavior including data races and memory corruption when multiple threads access the same AtomicBucket instance concurrently.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Metrics UtilApplication
< 0.7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate metrics-util version in Cargo.lockSearch your project's Cargo.lock file for the metrics-util entry and read the version number next to 'name = "metrics-util"'. Also check any Cargo.toml files that explicitly depend on metrics-util.Affected if The version is less than 0.7.0 (e.g., 0.6.0, 0.5.0, etc.)
-
Identify AtomicBucket usage in source codeSearch your codebase for imports or usage of AtomicBucket from metrics_util, such as 'use metrics_util::AtomicBucket' or references to 'AtomicBucket' type.Affected if The project directly imports or uses the AtomicBucket<T> type from metrics-util
-
Detect cross-thread AtomicBucket sharingSearch for patterns where AtomicBucket is wrapped in Arc, passed to spawn/spawn_blocking, or shared between threads via channels or mutexes. Look for Arc<AtomicBucket<T>>, thread::spawn closures capturing AtomicBucket, or similar constructs.Affected if The same AtomicBucket instance is accessed from multiple threads concurrently
-
Check dependent crates for vulnerable metrics-utilRun 'cargo tree -p metrics-util' or examine your full Cargo.lock to see all crates that depend on metrics-util and their required versions.Affected if Any dependent crate pulls in a version of metrics-util below 0.7.0
Your environment is affected if metrics-util version is below 0.7.0 AND your code uses AtomicBucket and shares it across threads.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped0.7.0
Upgrade metrics-util to version 0.7.0 or later, which contains the corrected trait implementations. Audit any dependent crates in the application that use metrics-util to ensure they also pull in the patched version.
metrics-util >= 0.7.0
- Locate your project's Cargo.toml file that declares metrics-util as a dependency
- Update the metrics-util version entry to ">=0.7.0" (e.g., metrics-util = "0.7.0" or metrics-util = ">=0.7.0")
- Run "cargo update metrics-util" to fetch the new version
- Run "cargo build" or "cargo check" to verify the upgrade compiles successfully
- Review the metrics-util changelog for version 0.7.0 to check for any API changes that may require code adjustments
- Run your test suite to ensure the upgrade does not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Metrics Util
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45704 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-45704 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data