CVE-2019-15545
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-core crate before 0.8.1 for Rust. Attackers can spoof ed25519 signatures.
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 libp2p-core Rust crate before version 0.8.1 contains a vulnerability that allows attackers to spoof ed25519 digital signatures. This cryptographic flaw undermines the authentication mechanism in any system relying on this library for signature verification, potentially allowing attackers to forge valid signatures and impersonate legitimate parties in peer-to-peer communications.
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>= 0.3, < 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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 libp2p-core in your project dependenciesSearch your project for Cargo.toml and Cargo.lock files. In Cargo.toml, look for libp2p-core under [dependencies] or [dev-dependencies] sections. In Cargo.lock, search for the [[package]] entry with name = "libp2p-core".Affected if The libp2p-core crate is listed as a direct or transitive dependency.
-
Determine the installed version of libp2p-coreRead the version field from the Cargo.toml dependency entry (for example: libp2p-core = "0.5.0") or the version line in the Cargo.lock [[package]] entry (for example: version = "0.5.0").Affected if The version listed is 0.8.0 or lower, or any version less than 0.8.1.
-
Check if ed25519 signature verification is in useSearch your codebase and any dependent code for references to ed25519 verification functions provided by libp2p-core. Look for uses of Ed25519, verify, or signature verification in the context of libp2p communications.Affected if Your code or any code using libp2p-core calls ed25519 signature verification functions.
-
Review transitive dependencies for libp2p-coreExamine your Cargo.lock file for any indirect (transitive) dependencies that may pull in libp2p-core. Check all [[package]] entries that list libp2p-core as a dependency.Affected if A transitive dependency is pulling in a vulnerable version of libp2p-core.
You are affected if your project has libp2p-core version 0.8.0 or lower (less than 0.8.1) as a dependency and your application or any dependent crate uses ed25519 signature verification from that library.
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.
From vendor data0.8.1
Upgrade the libp2p-core crate to version 0.8.1 or later to obtain the patched ed25519 signature verification. Review all code paths using ed25519 verification to ensure the vulnerability was not already exploited.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.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,936.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15545 — 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-2019-15545 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