CVE-2021-32961
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 · uneditedA getfile function in MDT AutoSave versions prior to v6.02.06 enables a user to supply an optional parameter, resulting in the processing of a request in a special manner. This can result in the execution of an unzip command and place a malicious .exe file in one of the locations the function looks for and get execution capabilities.
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 confidenceThe getfile function in MDT AutoSave prior to v6.02.06 accepts an optional parameter that triggers special processing, allowing an attacker to manipulate the function into executing an unzip command that places a malicious .exe file in a location where it can be executed, achieving remote code execution.
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< 6.02.06>= 7.00, <= 7.04< 4.01= 5.00CVSS 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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
-
Identify the installed MDT AutoSave versionCheck the application version through the software's About dialog, installation directory, or Windows Programs and Features. Common locations include the installation folder or registry keys under HKLM\Software\MDT Autosave or similar.Affected if The installed version falls within < 6.02.06, or >= 7.00 through <= 7.04 for standard MDT Autosave; or < 4.01 or = 5.00 for MDT Autosave For System Platform.
-
Determine if the web interface is exposedCheck if the MDT AutoSave web server (typically running on ports 8080, 8443, or similar) is accessible from the network. Review firewall rules and network segmentation settings.Affected if The web interface is accessible from untrusted networks, increasing exposure to remote exploitation.
-
Inspect the getfile function access logsReview web server access logs and application logs for requests to the getfile endpoint with unusual parameters, especially those containing zip file references or path traversal patterns.Affected if Logs show getfile requests with unexpected parameter values or patterns that suggest exploitation attempts.
-
Search for unauthorized executable filesUse file system auditing to scan common writable directories (such as the application web root, temp folders, or system directories) for newly created .exe files that were not part of the original installation.Affected if Unexpected .exe files are found in the application directory, web root, or system paths.
-
Review for suspicious processesMonitor running processes on the host for unfamiliar executables, especially those launched from application temp directories or unexpected locations.Affected if Unfamiliar processes are running, or processes are executing from paths associated with the MDT AutoSave application directories.
A user is affected if MDT AutoSave is installed with a version number matching the affected ranges AND the web interface is accessible, or if unauthorized .exe files or exploitation indicators are found on the system.
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.
dbcve · scoped4.016.02.06
Update MDT AutoSave to version 6.02.06 or later to remediate the vulnerability. Additionally, investigate the system for any malicious .exe files that may have been placed via this vulnerability and review access logs for indicators of compromise.
Autosave 6.02.06+ (or 7.05+ for 7.x branch); Autosave For System Platform 4.01+
- Identify the exact version of MDT AutoSave or Autosave For System Platform currently installed
- For Autosave versions < 6.02.06: upgrade to version 6.02.06 or later
- For Autosave versions 7.00-7.04: upgrade to version 7.05 or later
- For Autosave For System Platform: upgrade to version 4.01 or later
- After upgrading, verify the getfile function no longer allows arbitrary file upload and unzip operations
- Test that normal functionality of Autosave still works as expected after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32961 — 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-2021-32961 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