Vec ConstApplication · Vec Const Project
CVE-2021-45680
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 vec-const crate before 2.0.0 for Rust. It tries to construct a Vec from a pointer to a const slice, leading to memory corruption.
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 · moderate confidenceThe vec-const Rust crate before version 2.0.0 has a memory corruption vulnerability where it incorrectly attempts to construct a Vec from a pointer to a const slice. This improper pointer handling leads to undefined behavior and memory corruption.
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
Vec ConstApplication
< 2.0.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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 vec-const in project dependenciesSearch your project's Cargo.toml file for 'vec-const' in the [dependencies] section, and check Cargo.lock for any vec-const entries under [[package]]Affected if vec-const appears as a direct or transitive dependency
-
Identify the installed versionIn Cargo.lock, find the [[package]] entry with name = "vec-const" and read the version field (e.g., version = "1.2.3")Affected if The version is less than 2.0.0 (e.g., 1.x.y or 0.x.y)
-
Check for indirect dependenciesRun 'cargo tree -p vec-const' or 'cargo tree -i vec-const' to see if vec-const is pulled in as a transitive dependency by another crateAffected if vec-const appears as an indirect dependency at a vulnerable version
-
Verify the vulnerability trigger conditionReview code that calls vec-const functions, particularly any code that constructs a Vec from pointer/slice operations provided by this crateAffected if Your code uses vec-const to build Vec from const slice pointers
You are affected if vec-const version < 2.0.0 appears anywhere in your Cargo.lock as a direct or transitive dependency and your code actually invokes the vulnerable Vec construction functionality.
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 · scoped2.0.0
Upgrade the vec-const crate to version 2.0.0 or later in Cargo.toml and rebuild the project. Review any code using this crate for potential side effects.
vec-const version 2.0.0
- Update the vec-const dependency in Cargo.toml to version 2.0.0 or later
- Run cargo update or cargo build to fetch the fixed version
- Test the application to ensure functionality is maintained after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Vec Const
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45680 — 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-45680 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