Skip to content

← Public intelligence

NuGet package

starkbank-ecdsa

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.8NuGetPublished

    Improper Verification of Cryptographic Signature in starkbank-ecdsa

    CVE-2021-43569 · GHSA-j3jw-j2j8-2wv9

    Affected
    • NuGet starkbank-ecdsa < 1.3.2
    Fixed in
    1.3.2· Vendor fix available
    Issue
    The verify function in the Stark Bank .NET ECDSA library (ecdsa-dotnet) 1.3.1 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.

    Recommended action: Upgrade to 1.3.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. UnratedNuGetAmendedPublished

    Signature verification vulnerability in Stark Bank ecdsa libraries

    GHSA-9wx7-jrvc-28mm

    Affected
    • NuGet starkbank-ecdsa >= 1.3.1, <= 1.3.1
    Fixed in
    1.3.2· Vendor fix available
    Issue
    An attacker can forge signatures on arbitrary messages that will verify for any public key. This may allow attackers to authenticate as any user within the Stark Bank platform, and bypass signature verification needed to perform operations on the platform, such as send payments and transfer funds. Additionally, the ability for attackers to forge signatures may impact other users and projects using these libraries in different and unforeseen ways.

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

    Sources:osv.dev (1)github.com (2)Source checked Evidence →