Messagepack RsApplication · Messagepack Rs Project
CVE-2021-45690
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 messagepack-rs crate through 2021-01-26 for Rust. deserialize_binary may read from uninitialized memory locations.
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 deserialize_binary function in the messagepack-rs crate reads from uninitialized memory locations, which could allow an attacker to obtain sensitive information from memory or cause undefined behavior during deserialization of maliciously crafted MessagePack data.
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
Messagepack RsApplication
< 0.8.1CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/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.
-
Identify if messagepack-rs is a dependencyRun 'cargo tree' in your project directory to check if the messagepack-rs crate appears in your dependency tree, or inspect your Cargo.lock file for a messagepack-rs entryAffected if messagepack-rs appears in your dependency tree
-
Determine the installed version of messagepack-rsCheck the version number in Cargo.lock under the messagepack-rs entry, or run 'cargo list --format=json' and look for messagepack-rsAffected if the version is less than 0.8.1
-
Check for usage of the deserialize_binary functionSearch your codebase for calls to 'deserialize_binary' from the messagepack-rs crate, using grep or similar tool with patterns like 'deserialize_binary'Affected if your code calls the deserialize_binary function on MessagePack data
-
Determine if external or untrusted MessagePack data is being deserializedReview code paths where deserialize_binary is called and identify whether the input originates from external sources, user input, network connections, or files that could contain malicious dataAffected if deserialize_binary processes data from untrusted or external sources such as network input, user-uploaded files, or inter-process communication
You are affected if messagepack-rs with version less than 0.8.1 is in your dependency tree AND your code uses the deserialize_binary function to process untrusted or external MessagePack data.
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.8.1
Update to a patched version of messagepack-rs when available; otherwise, implement strict input validation on MessagePack data before deserialization and consider alternative serialization libraries.
0.8.1
- Update Cargo.toml dependency for messagepack-rs to version 0.8.1 or later
- Run `cargo update messagepack-rs` to fetch the fixed version
- Rebuild the project with `cargo build` to verify the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Messagepack Rs
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-45690 — 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-45690 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