Real Time Logic SharkSSL up to 09.09.24 TLS Client Key Exchange Message heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Real Time Logic SharkSSL up to 09.09.24 and classified as critical. The affected element is an unknown function of the component TLS Client Key Exchange Message Handler. Performing a manipulation results in heap-based overflow. This vulnerability is identified as CVE-2024-48075. The attack can be initiated remotely. There is not any exploit available. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability classified as critical has been found in Real Time Logic SharkSSL up to 09.09.24. This affects an unknown part of the component TLS Client Key Exchange Message Handler. The manipulation with an unknown input leads to a heap-based overflow vulnerability. CWE is classifying the issue as CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). This is going to have an impact on availability. The summary by CVE is:
A Heap buffer overflow in the server-site handshake implementation in Real Time Logic SharkSSL 09.09.24 and earlier allows a remote attacker to trigger a Denial-of-Service via a malformed TLS Client Key Exchange message.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-48075 since 10/08/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Neither technical details nor an exploit are publicly available.
Applying the patch 7045f6f254060640ff77eef2027f108fcc20e2f2 is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
- 09.09.0
- 09.09.1
- 09.09.2
- 09.09.3
- 09.09.4
- 09.09.5
- 09.09.6
- 09.09.7
- 09.09.8
- 09.09.9
- 09.09.10
- 09.09.11
- 09.09.12
- 09.09.13
- 09.09.14
- 09.09.15
- 09.09.16
- 09.09.17
- 09.09.18
- 09.09.19
- 09.09.20
- 09.09.21
- 09.09.22
- 09.09.23
- 09.09.24
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (MITRE): 🔍
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: Heap-based overflowCWE: CWE-122 / 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: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 7045f6f254060640ff77eef2027f108fcc20e2f2
Timeline
10/08/2024 🔍11/13/2024 🔍
11/13/2024 🔍
11/19/2024 🔍
Sources
Advisory: 7045f6f254060640ff77eef2027f108fcc20e2f2Status: Confirmed
CVE: CVE-2024-48075 (🔍)
GCVE (CVE): GCVE-0-2024-48075
GCVE (VulDB): GCVE-100-284301
Entry
Created: 11/13/2024 08:58Updated: 11/19/2024 07:09
Changes: 11/13/2024 08:58 (57), 11/19/2024 07:09 (11)
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.