ZLMediaKit up to 8.0 HTTP API Interface secret hard-coded password
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in ZLMediaKit up to 8.0. Affected is an unknown function of the component HTTP API Interface. This manipulation of the argument secret causes hard-coded password. This vulnerability is tracked as CVE-2024-27488. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as problematic was found in ZLMediaKit up to 8.0. Affected by this vulnerability is an unknown functionality of the component HTTP API Interface. The manipulation of the argument secret with an unknown input leads to a hard-coded password vulnerability. The CWE definition for the vulnerability is CWE-259. The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components. As an impact it is known to affect confidentiality. The summary by CVE is:
Incorrect Access Control vulnerability in ZLMediaKit versions 1.0 through 8.0, allows remote attackers to escalate privileges and obtain sensitive information. The application system enables the http API interface by default and uses the secret parameter method to authenticate the http restful api interface, but the secret is hardcoded by default.
It is possible to read the advisory at gist.github.com. This vulnerability is known as CVE-2024-27488 since 02/26/2024. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details of the vulnerability are known, but there is no available exploit. The attack technique deployed by this issue is T1078.001 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.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.6VulDB Meta Temp Score: 7.4
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 9.8
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: Hard-coded passwordCWE: CWE-259 / CWE-255
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
02/26/2024 🔍04/08/2024 🔍
04/08/2024 🔍
08/22/2024 🔍
Sources
Advisory: gist.github.comStatus: Not defined
CVE: CVE-2024-27488 (🔍)
GCVE (CVE): GCVE-0-2024-27488
GCVE (VulDB): GCVE-100-259687
Entry
Created: 04/08/2024 08:31Updated: 08/22/2024 20:11
Changes: 04/08/2024 08:31 (52), 08/22/2024 20:11 (13)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.