Macrovideo v380pro 1.4.97 device id/password privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Macrovideo v380pro 1.4.97. It has been classified as problematic. This issue affects some unknown processing. The manipulation of the argument device id/password leads to an unknown weakness. This vulnerability is listed as CVE-2023-33741. There is no available exploit.
Details
A vulnerability was found in Macrovideo v380pro 1.4.97 and classified as problematic. The manipulation of the argument device id/password with an unknown input leads to a unknown weakness. The impact remains unknown. The summary by CVE is:
Macrovideo v380pro v1.4.97 shares the device id and password when sharing the device.
The weakness was presented 05/31/2023. The advisory is shared at github.com. The identification of this vulnerability is CVE-2023-33741 since 05/22/2023. Technical details are known, but no exploit is available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2023-37893). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.8
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CNA Base Score: 7.5
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: Privilege escalationCWE: Unknown
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
05/22/2023 🔍05/31/2023 🔍
05/31/2023 🔍
01/06/2026 🔍
Sources
Advisory: github.comStatus: Not defined
CVE: CVE-2023-33741 (🔍)
GCVE (CVE): GCVE-0-2023-33741
GCVE (VulDB): GCVE-100-230333
EUVD: 🔍
Entry
Created: 05/31/2023 09:59Updated: 01/06/2026 12:49
Changes: 05/31/2023 09:59 (36), 06/25/2023 01:24 (11), 01/13/2025 20:43 (25), 01/06/2026 12:49 (1)
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.