CVE-2021-32937
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 · uneditedAn attacker can gain knowledge of a session temporary working folder where the getfile and putfile commands are used in MDT AutoSave versions prior to v6.02.06. An attacker can leverage this knowledge to provide a malicious command to the working directory where the read and write activity can be initiated.
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 · high confidenceAn information disclosure vulnerability in MDT AutoSave versions prior to v6.02.06 allows attackers to discover the session temporary working folder used by getfile and putfile commands. This knowledge can be exploited to inject malicious commands into the working directory, enabling unauthorized read and write activity.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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.
-
Locate MDT AutoSave installation directoryCheck the default installation path (typically C:\Program Files\Auvesy\MDT AutoSave or C:\Program Files (x86)\Auvesy\MDT AutoSave) and look for the executable file (AutoSave.exe or similar).Affected if The application is installed in any version.
-
Identify installed version numberRight-click the AutoSave executable, select Properties, then go to the Details tab to view the Product Version. Alternatively, open Windows Control Panel > Programs and Features, find Auvesy MDT AutoSave in the list, and note the version shown.Affected if The version cannot be determined or is not visible.
-
Compare version against affected rangesFor standard MDT AutoSave: check if version is less than 6.02.06, OR if version is 7.00 through 7.04. For MDT AutoSave for System Platform: check if version is less than 4.01, OR if version equals 5.00.Affected if The installed version falls into any of these ranges: < 6.02.06, 7.00-7.04, < 4.01 (System Platform), or 5.00 (System Platform).
You are affected if Auvesy MDT AutoSave (or MDT AutoSave for System Platform) is installed and the version number matches any of the vulnerable ranges listed.
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
Upgrade MDT AutoSave to version 6.02.06 or later to remediate this vulnerability.
Autosave: v6.02.06 or later (or latest 7.x release); Autosave For System Platform: v4.01 or later
- Identify which Autosave product is in use: Autosave or Autosave For System Platform
- For Autosave: Upgrade to version 6.02.06 or later
- For Autosave For System Platform: Upgrade to version 4.01 or later
- After upgrading, verify that the session temporary working folder information is no longer exposed through error messages
- Test that getfile and putfile commands function correctly after the upgrade
- Ensure the system is running the latest supported release within the respective major version branch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-32937 — 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-32937 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