CVE-2023-38355
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMiniTool Movie Maker 7.0 contains an insecure installation process that allows attackers to achieve remote code execution through a man in the middle attack.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMiniTool Movie Maker 7.0 has an insecure installation process that downloads components over unencrypted or unauthenticated channels, allowing a man-in-the-middle attacker to intercept the download and inject malicious code. Successful exploitation grants the attacker remote code execution on the victim's machine during the installation process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 7.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm MiniTool Movie Maker is installedOpen Control Panel > Programs and Features, or search for 'MiniTool Movie Maker' in the Start menu. Look for the application in the installed programs list.Affected if MiniTool Movie Maker version 7.0 appears in the installed programs
-
Verify the installed version numberRight-click the MiniTool Movie Maker shortcut or executable, select Properties, then go to the Details tab to check the Product Version. Alternatively, right-click the installed exe file and select Properties.Affected if The version is listed as exactly 7.0
-
Check installer source and network behaviorReview installation logs in %TEMP% or %APPDATA% for records of the original installer. Examine network traffic captures or proxy logs if available, looking for HTTP (not HTTPS) connections during the original installation time.Affected if The installer was downloaded over HTTP or an unsecured connection, or network logs show unencrypted download activity during installation
-
Inspect for unexpected installed componentsCheck the installation directory (typically C:\Program Files\MiniTool\Movie Maker or C:\Program Files (x86)\MiniTool\Movie Maker) for unexpected DLLs, executables, or scripts that were not part of the original package.Affected if Unexpected files or components exist in the installation directory that were not part of the official installer
A user is affected if MiniTool Movie Maker version 7.0 is installed and the original installation involved downloading components over unencrypted HTTP connections, exposing the process to potential man-in-the-middle injection.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataAvoid using MiniTool Movie Maker 7.0 until an official patch is released. If use is required, perform installations on isolated networks and verify installer integrity via checksums from trusted sources. Consider using alternative video editing software with secure update mechanisms.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38355 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-38355 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data