Arm Mbed Crypto/mbed TLS up to 2.1 ECDSA ecdsa.c information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.6 | $0-$5k | 0.00 |
Summary
A vulnerability described as problematic has been identified in Arm Mbed Crypto and mbed TLS up to 2.1. Affected is an unknown function of the file ecdsa.c of the component ECDSA Handler. The manipulation results in information disclosure. This vulnerability is known as CVE-2019-18222. Attacking locally is a requirement. No exploit is available.
Details
A vulnerability was found in Arm Mbed Crypto and mbed TLS up to 2.1. It has been classified as problematic. Affected is an unknown code block of the file ecdsa.c of the component ECDSA Handler. The manipulation with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. CVE summarizes:
The ECDSA signature implementation in ecdsa.c in Arm Mbed Crypto 2.1 and Mbed TLS through 2.19.1 does not reduce the blinded scalar before computing the inverse, which allows a local attacker to recover the private key via side-channel attacks.
The weakness was published 01/23/2020 (Website). The advisory is shared for download at tls.mbed.org. This vulnerability is traded as CVE-2019-18222 since 10/21/2019. The exploitability is told to be difficult. The attack needs to be approached locally. The requirement for exploitation is a authentication. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1592.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.6VulDB Meta Temp Score: 3.6
VulDB Base Score: 2.5
VulDB Temp Score: 2.5
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 4.7
NVD Vector: 🔍
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: 🔍
NVD Base Score: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
10/21/2019 🔍01/23/2020 🔍
01/24/2020 🔍
03/25/2024 🔍
Sources
Advisory: DLA 3249-1Status: Not defined
CVE: CVE-2019-18222 (🔍)
GCVE (CVE): GCVE-0-2019-18222
GCVE (VulDB): GCVE-100-149280
Entry
Created: 01/24/2020 08:37Updated: 03/25/2024 14:56
Changes: 01/24/2020 08:37 (38), 01/24/2020 08:42 (17), 03/25/2024 14:56 (17)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.