Skip to content

Improper Verification of Cryptographic Signature in starkbank-ecdsa

Critical severity GitHub Reviewed Published Nov 10, 2021 to the GitHub Advisory Database • Updated Feb 1, 2023

Package

nuget starkbank-ecdsa (NuGet)

Affected versions

< 1.3.2

Patched versions

1.3.2

Description

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.

References

Published by the National Vulnerability Database Nov 9, 2021
Reviewed Nov 10, 2021
Published to the GitHub Advisory Database Nov 10, 2021
Last updated Feb 1, 2023

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

0.404%
(74th percentile)

Weaknesses

CVE ID

CVE-2021-43569

GHSA ID

GHSA-j3jw-j2j8-2wv9

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.