Libp2p DeflateApplication · Libp2p
CVE-2020-36443
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 libp2p-deflate crate before 0.27.1 for Rust. An uninitialized buffer is passed to AsyncRead::poll_read(), which is a user-provided trait function.
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 libp2p-deflate crate before version 0.27.1 passes an uninitialized buffer to the user-provided AsyncRead::poll_read() trait implementation. This can leak uninitialized memory contents to callback callers or cause undefined behavior.
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
Libp2p DeflateApplication
< 0.27.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.
-
Locate the libp2p-deflate dependency in your projectSearch your project's Cargo.lock file for 'libp2p-deflate' and note the version number listed (e.g., name = "libp2p-deflate" version = "0.27.0")Affected if the version is less than 0.27.1
-
Verify the dependency is actually usedCheck your Cargo.toml files for a direct or transitive dependency on libp2p-deflate, or check if your project imports and uses deflate transport (look for 'libp2p_deflate' or 'deflate::' in your source code)Affected if the crate is present in dependencies and your code uses the deflate transport module
You are affected if your project depends on libp2p-deflate with a version lower than 0.27.1 and your code actually invokes the deflate transport 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 · scoped0.27.1
Upgrade libp2p-deflate to version 0.27.1 or later, which properly initializes the buffer before passing it to poll_read().
0.27.1
- Update the libp2p-deflate dependency in your Cargo.toml file to version 0.27.1 or later (e.g., libp2p-deflate = "0.27.1")
- Run `cargo update libp2p-deflate` to update the lockfile
- Run `cargo build` or `cargo check` to verify the upgrade compiles successfully
- Review the crate changelog for any relevant changes between your current version and 0.27.1
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Libp2p Deflate
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-36443 — 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-2020-36443 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