MiniTool Movie Maker up to 6.1.0 Installation channel accessible
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.2 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in MiniTool Movie Maker up to 6.1.0. This affects an unknown function of the component Installation Handler. Performing a manipulation results in channel accessible. This vulnerability was named CVE-2023-38355. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in MiniTool Movie Maker up to 6.1.0. It has been classified as critical. This affects some unknown processing of the component Installation Handler. The manipulation with an unknown input leads to a channel accessible vulnerability. CWE is classifying the issue as CWE-300. The product does not adequately verify the identity of actors at both ends of a communication channel, or does not adequately ensure the integrity of the channel, in a way that allows the channel to be accessed or influenced by an actor that is not an endpoint. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
MiniTool Movie Maker 6.1.0 contains an insecure installation process that allows attackers to achieve remote code execution through a man in the middle attack.
The weakness was presented 09/19/2023. The advisory is shared at 0dr3f.github.io. This vulnerability is uniquely identified as CVE-2023-38355 since 07/15/2023. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/19/2026). MITRE ATT&CK project uses the attack technique T1557 for this issue.
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-42172). 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: 7.2VulDB Meta Temp Score: 7.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.1
NVD 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: Channel accessibleCWE: CWE-300
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
07/15/2023 🔍09/19/2023 🔍
09/19/2023 🔍
01/19/2026 🔍
Sources
Advisory: 0dr3f.github.ioStatus: Not defined
CVE: CVE-2023-38355 (🔍)
GCVE (CVE): GCVE-0-2023-38355
GCVE (VulDB): GCVE-100-239973
EUVD: 🔍
Entry
Created: 09/19/2023 19:10Updated: 01/19/2026 06:48
Changes: 09/19/2023 19:10 (37), 10/13/2023 08:45 (11), 01/19/2026 06:48 (16)
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.