Home
» GitHub Advisories
» GHSA-92vm-mxjf-jqf3
Description
The verify function in the Stark Bank Python ECDSA library (starkbank-ecdsa) 2.0.0 fails to check that the signature is non-zero, which allows attackers to forge signatures on arbitrary messages.
Basic information
Type
reviewed
Severity
critical Advisory on GitHub
Open advisory ↗ Repository advisory
—
Source code
Browse source ↗ Published (advisory)
2021-11-10 20:41:39 UTC
Updated
2024-10-25 14:49:42 UTC
GitHub reviewed
2021-11-10 18:23:18 UTC
NVD published
2021-11-09
EPSS Score
Score
Percentile
0.24%
47.26%
CVSS Scores
Base score
Version
Severity
Vector
9.8
3.1
—
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
CWEs
CWE id
Name
CWE-347
Improper Verification of Cryptographic Signature
Affected packages (1)
Vulnerable version ranges and first patched releases as published by GitHub.
Ecosystem
Package
Vulnerable range
First patched
Vulnerable functions
pip
starkbank-ecdsa < 2.0.1
2.0.1
—
cvelogic
Threat Intelligence