Skip to content

← Public intelligence

crates.io package

libsecp256k1

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. Critical, CVSS 9.8crates.ioPublished

    Overflow in libsecp256k1

    CVE-2021-38195 · GHSA-g4vj-x7v9-h82m

    Affected
    • crates.io libsecp256k1 < 0.5.0
    Fixed in
    0.5.0· Vendor fix available
    Issue
    An issue was discovered in the libsecp256k1 crate before 0.5.0 for Rust. It can verify an invalid signature because it allows the R or S parameter to be larger than the curve order, aka an overflow.

    Recommended action: Upgrade to 0.5.0 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

    libsecp256k1 contains side-channel timing attack

    CVE-2019-25003 · GHSA-hrjm-c879-pp86

    Affected
    • crates.io libsecp256k1 < 0.3.1
    Fixed in
    0.3.1· Vendor fix available
    Issue
    Versions of libsecp256k1 prior to 0.3.1 did not execute Scalar::checkoverflow in constant time. This allows an attacker to potentially leak information via a timing attack. The flaw was corrected by modifying Scalar::checkoverflow to execute in constant time.

    Recommended action: Upgrade to 0.3.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 →