ARM mbedTLS up to 2.7.0 library/ssl_tls.c:7142 ssl_write_real Data Loss input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in ARM mbedTLS up to 2.7.0. Affected is the function ssl_write_real of the file library/ssl_tls.c:7142. This manipulation causes input validation (Data Loss).
This vulnerability is handled as CVE-2018-1000061. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability was found in ARM mbedTLS up to 2.7.0. It has been declared as problematic. Affected by this vulnerability is the function ssl_write_real of the file library/ssl_tls.c:7142. The manipulation with an unknown input leads to a input validation vulnerability (Data Loss). The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does
not validate or incorrectly validates that the input has the
properties that are required to process the data safely and
correctly. As an impact it is known to affect availability. The summary by CVE is:
ARM mbedTLS version development branch, 2.7.0 and earlier contains a CWE-670, Incorrect condition control flow leading to incorrect return, leading to data loss vulnerability in ssl_write_real(), library/ssl_tls.c:7142 that can result in Leads to data loss, can be escalated to DoS and authorization bypass in application protocols. This attack appear to be exploitable via network connectivity.
The bug was discovered 02/09/2018. The weakness was released 02/09/2018 (GitHub Repository). The advisory is shared at github.com. This vulnerability is known as CVE-2018-1000061 since 02/09/2018. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.9
VulDB Base Score: 5.3
VulDB Temp Score: 4.9
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: 🔍
NVD Base Score: 🔍
Exploiting
Name: Data LossClass: Input validation / Data Loss
CWE: CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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
02/09/2018 🔍02/09/2018 🔍
02/09/2018 🔍
02/09/2018 🔍
02/10/2018 🔍
02/06/2023 🔍
Sources
Advisory: 1356Status: Not defined
CVE: CVE-2018-1000061 (🔍)
GCVE (CVE): GCVE-0-2018-1000061
GCVE (VulDB): GCVE-100-113101
Entry
Created: 02/10/2018 10:58Updated: 02/06/2023 11:24
Changes: 02/10/2018 10:58 (42), 01/03/2020 16:35 (7), 02/06/2023 11:24 (3)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.