ThroughTek Kalay SDK up to 3.1.10.16/3.3.6.1/3.4.7.3/4.3.3.1 PSK Identity uninitialized variable
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.7 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in ThroughTek Kalay SDK up to 3.1.10.16/3.3.6.1/3.4.7.3/4.3.3.1. Affected by this vulnerability is an unknown functionality of the component PSK Identity Handler. The manipulation leads to uninitialized variable. This vulnerability is listed as CVE-2023-6324. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in ThroughTek Kalay SDK up to 3.1.10.16/3.3.6.1/3.4.7.3/4.3.3.1. It has been rated as critical. This issue affects some unknown processing of the component PSK Identity Handler. The manipulation with an unknown input leads to a uninitialized variable vulnerability. Using CWE to declare the problem leads to CWE-457. The code uses a variable that has not been initialized, leading to unpredictable or unintended results. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
ThroughTek Kalay SDK uses a predictable PSK value in the DTLS session when encountering an unexpected PSK identity
The weakness was presented by Alexandru Lazar. The advisory is shared at bitdefender.com. The identification of this vulnerability is CVE-2023-6324 since 11/27/2023. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 3.1.10.0
- 3.1.10.1
- 3.1.10.2
- 3.1.10.3
- 3.1.10.4
- 3.1.10.5
- 3.1.10.6
- 3.1.10.7
- 3.1.10.8
- 3.1.10.9
- 3.1.10.10
- 3.1.10.11
- 3.1.10.12
- 3.1.10.13
- 3.1.10.14
- 3.1.10.15
- 3.1.10.16
- 3.3.6.0
- 3.3.6.1
- 3.4.7.0
- 3.4.7.1
- 3.4.7.2
- 3.4.7.3
- 4.3.3.0
- 4.3.3.1
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.7VulDB Meta Temp Score: 7.7
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CNA Base Score: 8.1
CNA 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: 🔍
Exploiting
Class: Uninitialized variableCWE: CWE-457 / CWE-453
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: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
11/27/2023 🔍05/15/2024 🔍
05/15/2024 🔍
02/12/2025 🔍
Sources
Advisory: bitdefender.comResearcher: Alexandru Lazar
Status: Not defined
CVE: CVE-2023-6324 (🔍)
GCVE (CVE): GCVE-0-2023-6324
GCVE (VulDB): GCVE-100-264473
Entry
Created: 05/15/2024 14:59Updated: 02/12/2025 09:30
Changes: 05/15/2024 14:59 (61), 02/12/2025 09:30 (12)
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.