HCL Launch up to 7.0.5.18/7.1.2.14/7.2.3.7/7.3.2.2 Archive File resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in HCL Launch up to 7.0.5.18/7.1.2.14/7.2.3.7/7.3.2.2. It has been rated as problematic. This affects an unknown function of the component Archive File Handler. Performing a manipulation results in resource consumption. This vulnerability is cataloged as CVE-2023-45703. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability, which was classified as problematic, was found in HCL Launch up to 7.0.5.18/7.1.2.14/7.2.3.7/7.3.2.2. This affects an unknown function of the component Archive File Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. CWE is classifying the issue as CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. This is going to have an impact on availability. The summary by CVE is:
HCL Launch may mishandle input validation of an uploaded archive file leading to a denial of service due to resource exhaustion.
The weakness was shared 12/21/2023 as KB0108649. It is possible to read the advisory at support.hcltechsw.com. This vulnerability is uniquely identified as CVE-2023-45703 since 10/10/2023. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1499 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
Version
- 7.0.5.0
- 7.0.5.1
- 7.0.5.2
- 7.0.5.3
- 7.0.5.4
- 7.0.5.5
- 7.0.5.6
- 7.0.5.7
- 7.0.5.8
- 7.0.5.9
- 7.0.5.10
- 7.0.5.11
- 7.0.5.12
- 7.0.5.13
- 7.0.5.14
- 7.0.5.15
- 7.0.5.16
- 7.0.5.17
- 7.0.5.18
- 7.1.2.0
- 7.1.2.1
- 7.1.2.2
- 7.1.2.3
- 7.1.2.4
- 7.1.2.5
- 7.1.2.6
- 7.1.2.7
- 7.1.2.8
- 7.1.2.9
- 7.1.2.10
- 7.1.2.11
- 7.1.2.12
- 7.1.2.13
- 7.1.2.14
- 7.2.3.0
- 7.2.3.1
- 7.2.3.2
- 7.2.3.3
- 7.2.3.4
- 7.2.3.5
- 7.2.3.6
- 7.2.3.7
- 7.3.2.0
- 7.3.2.1
- 7.3.2.2
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.3
VulDB Base Score: 3.1
VulDB Temp Score: 3.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 5.3
CNA Vector (HCL Software): 🔍
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: Resource consumptionCWE: CWE-400 / CWE-404
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
10/10/2023 🔍12/21/2023 🔍
12/21/2023 🔍
01/14/2024 🔍
Sources
Advisory: KB0108649Status: Confirmed
CVE: CVE-2023-45703 (🔍)
GCVE (CVE): GCVE-0-2023-45703
GCVE (VulDB): GCVE-100-248619
Entry
Created: 12/21/2023 07:25Updated: 01/14/2024 08:46
Changes: 12/21/2023 07:25 (49), 01/14/2024 08:46 (11)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.