Skip to content

← Public intelligence

crates.io package

libp2p-core

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Unratedcrates.ioPublished

    Failure to verify the public key of a SignedEnvelope against the PeerId in a PeerRecord

    GHSA-wc36-xgcc-jwpr

    Affected
    • crates.io libp2p-core >= 0.30.0-rc.1, < 0.30.2
    Fixed in
    0.30.2· Vendor fix available
    Issue
    Affected versions of this crate did not check that the public key the signature was created with matches the peer ID of the peer record. Any combination was considered valid. This allows an attacker to republish an existing PeerRecord with a different PeerId.

    Recommended action: Upgrade to 0.30.2 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5crates.ioPublished

    Failure to properly verify ed25519 signatures in libp2p-core

    CVE-2019-15545 · GHSA-4q4x-67hx-5mpg

    Affected
    • crates.io libp2p-core < 0.8.1
    Fixed in
    0.8.1· Vendor fix available
    Issue
    Affected versions of this crate did not properly verify ed25519 signatures. Any signature with a correct length was considered valid. This allows an attacker to impersonate any node identity.

    Recommended action: Upgrade to 0.8.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →