Stark Bank ecdsa-java 1.0.0 Message verify signature verification
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.4 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic has been found in Stark Bank ecdsa-java 1.0.0. This issue affects the function verify of the component Message Handler. Performing a manipulation results in signature verification.
This vulnerability is known as CVE-2021-43570. No exploit is available.
It is recommended to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, was found in Stark Bank ecdsa-java 1.0.0 (Banking Software). This affects the function verify of the component Message Handler. The manipulation with an unknown input leads to a signature verification vulnerability. CWE is classifying the issue as CWE-347. The product does not verify, or incorrectly verifies, the cryptographic signature for data. This is going to have an impact on confidentiality, integrity, and availability.
The weakness was published 11/10/2021. The advisory is shared at research.nccgroup.com. This vulnerability is uniquely identified as CVE-2021-43570 since 11/09/2021. Technical details are known, but no exploit is available.
Upgrading to version 1.0.1 eliminates this vulnerability. The upgrade is hosted for download at github.com.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.6VulDB Meta Temp Score: 4.4
VulDB Base Score: 4.6
VulDB Temp Score: 4.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Signature verificationCWE: CWE-347 / CWE-345
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Partially
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: ecdsa-java 1.0.1
Timeline
11/09/2021 🔍11/10/2021 🔍
11/10/2021 🔍
11/12/2021 🔍
Sources
Advisory: research.nccgroup.comStatus: Confirmed
CVE: CVE-2021-43570 (🔍)
GCVE (CVE): GCVE-0-2021-43570
GCVE (VulDB): GCVE-100-186465
Entry
Created: 11/10/2021 13:06Updated: 11/12/2021 11:47
Changes: 11/10/2021 13:06 (42), 11/12/2021 11:47 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.