Libp2pApplication · Protocol
CVE-2022-23486
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 · uneditedlibp2p-rust is the official rust language Implementation of the libp2p networking stack. In versions prior to 0.45.1 an attacker node can cause a victim node to allocate a large number of small memory chunks, which can ultimately lead to the victim’s process running out of memory and thus getting killed by its operating system. When executed continuously, this can lead to a denial of service attack, especially relevant on a larger scale when run against more than one node of a libp2p based network. Users are advised to upgrade to `libp2p` `v0.45.1` or above. Users unable to upgrade should reference the DoS Mitigation page for more information on how to incorporate mitigation strategies, monitor their application, and respond to attacks: https://docs.libp2p.io/reference/dos-mitigation/.
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 confidenceIn libp2p-rust versions prior to 0.45.1, an attacker node can trigger a victim node to allocate an excessive number of small memory chunks, causing memory exhaustion. The victim's process can be terminated by the OS due to out-of-memory conditions, enabling denial of service attacks when exploited repeatedly against network nodes.
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
Libp2pApplication
< 0.45.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
- 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.
-
Identify libp2p dependency in your projectReview your Cargo.toml or lock file for the libp2p crate and note the version number specifiedAffected if The version listed is less than 0.45.1 (e.g., 0.45.0, 0.44.x, etc.)
-
Verify the actual resolved versionCheck your Cargo.lock file for the resolved libp2p version, as transitive dependencies or overrides may differ from what's declared in Cargo.tomlAffected if The resolved version in Cargo.lock is below 0.45.1
-
Confirm your application exposes libp2p to the networkReview your configuration to determine if your libp2p node accepts incoming connections from remote peersAffected if Your node listens for and accepts connections from untrusted network peers on any transport
-
Check if peer authentication is enforcedInspect your connection handler or security settings to verify if peer validation or authentication is required before accepting inbound connectionsAffected if No peer authentication or strict validation is configured for inbound connections
You are affected if your deployed libp2p version is below 0.45.1 AND your node accepts connections from untrusted remote peers.
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.45.1
Upgrade libp2p to version 0.45.1 or higher. If upgrading is not feasible, implement DoS mitigation strategies as documented in the libp2p DoS Mitigation guide and monitor application memory usage.
libp2p v0.45.1 or above
- Check the current version of libp2p in your project (typically in Cargo.toml)
- Update the libp2p dependency to version 0.45.1 or higher in your Cargo.toml file (e.g., libp2p = "0.45.1")
- Run `cargo update` or `cargo build` to fetch the new dependency
- Rebuild and test your application to verify compatibility with the updated library
- Deploy the updated application
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Libp2p
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23486 — 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-2022-23486 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