Cameron Hamilton-Rich axTLS up to 2.1.4 TLS Packet tls1.c need_bytes memory corruption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in Cameron Hamilton-Rich axTLS up to 2.1.4. Affected by this issue is some unknown functionality of the file tls1.c of the component TLS Packet Handler. Executing a manipulation of the argument need_bytes can lead to memory corruption. This vulnerability is tracked as CVE-2019-8981. The attack can be launched remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability has been found in Cameron Hamilton-Rich axTLS up to 2.1.4 and classified as critical. This vulnerability affects some unknown functionality of the file tls1.c of the component TLS Packet Handler. The manipulation of the argument need_bytes with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
tls1.c in Cameron Hamilton-Rich axTLS before 2.1.5 has a Buffer Overflow via a crafted sequence of TLS packets because the need_bytes value is mismanaged.
The bug was discovered 03/22/2019. The weakness was disclosed 03/26/2019. This vulnerability was named CVE-2019-8981 since 02/21/2019. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available.
The vulnerability was handled as a non-public zero-day exploit for at least 4 days. During that time the estimated underground price was around $0-$5k.
Upgrading to version 2.1.5 eliminates this vulnerability.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.8
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: Memory corruptionCWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
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: axTLS 2.1.5
Timeline
02/21/2019 🔍03/22/2019 🔍
03/26/2019 🔍
03/26/2019 🔍
08/07/2023 🔍
Sources
Advisory: axtls.sourceforge.netStatus: Not defined
CVE: CVE-2019-8981 (🔍)
GCVE (CVE): GCVE-0-2019-8981
GCVE (VulDB): GCVE-100-132232
Entry
Created: 03/26/2019 14:17Updated: 08/07/2023 13:22
Changes: 03/26/2019 14:17 (57), 05/20/2020 09:30 (1), 08/07/2023 13:22 (4)
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.