dbcve.org
AutosaveApplication · Auvesy Mdt

CVE-2021-32949

HIGH · 7.5 CVSS v3.1 Published 2022-04-01
Fix available
A fix is available. Upgrade to 4.01 / 6.02.06 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
An attacker could utilize a function in MDT AutoSave versions prior to v6.02.06 that permits changing a designated path to another path and traversing the directory, allowing the replacement of an existing file with a malicious file.

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 confidence

MDT AutoSave versions prior to v6.02.06 contain a path traversal vulnerability in a function that allows users to change a designated file path. By manipulating the path with directory traversal sequences (e.g., ../), an attacker can write arbitrary files to locations outside the intended directory, potentially overwriting system files or deploying malicious payloads.

MitigationUpgrade to MDT AutoSave v6.02.06 or later which contains the patch for this vulnerability. If immediate upgrade is not possible, implement input validation and access controls on file operations to prevent directory traversal.

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
AutosaveApplication
Affected:< 6.02.06>= 7.00, <= 7.04
Autosave For System PlatformApplication
Affected:< 4.01= 5.00

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed MDT AutoSave version
    Locate the MDT AutoSave installation and retrieve the version information, typically found in the software's about dialog, installation directory, or system registry entry for the program
    Affected if The installed version is any version prior to 6.02.06, or any version from 7.00 through 7.04, or any version prior to 4.01 for System Platform variant, or exactly version 5.00 for System Platform variant
  2. Confirm the product variant
    Determine whether the installation is standard MDT AutoSave or MDT AutoSave For System Platform, as each has distinct affected version ranges
    Affected if Running MDT AutoSave For System Platform versions 5.00 or versions prior to 4.01
  3. Verify if the file path modification feature is accessible
    Check whether the function that allows users to change a designated file path is enabled and accessible to users or processes
    Affected if The file path change feature is active and accepts user-supplied input without validation
  4. Inspect recent file write operations
    Review system logs, application logs, or file system activity for any write operations that occurred outside the intended designated directory, particularly looking for files written using directory traversal sequences
    Affected if Any file writes detected outside the expected directory bounds, or files containing ../ patterns in their paths

A user is affected if their installed version falls within the affected ranges (prior to 6.02.06, or 7.00-7.04 for main product; or prior to 4.01 or exactly 5.00 for System Platform) AND the file path modification feature is accessible and operational in their environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 4.01 / 6.02.06 or later
Fixed in 4.016.02.06
Interim mitigation

Upgrade to MDT AutoSave v6.02.06 or later which contains the patch for this vulnerability. If immediate upgrade is not possible, implement input validation and access controls on file operations to prevent directory traversal.

Recommended fix Moderate confidence

Autosave: v6.02.06 or later (or version beyond 7.04); Autosave For System Platform: v4.01 or later

  1. 1. Identify the currently installed MDT AutoSave product and version in your environment
  2. 2. If using Autosave, verify if version is < 6.02.06 or between 7.00 and 7.04 (inclusive)
  3. 3. If using Autosave For System Platform, verify if version is < 4.01 or equals 5.00
  4. 4. Obtain the appropriate fixed version: Upgrade Autosave to v6.02.06 or later (for version 7.x, upgrade to a version beyond 7.04)
  5. 5. For Autosave For System Platform, upgrade to v4.01 or later
  6. 6. Download the patched version from the official vendor (Schneider Electric) or through your normal update channel
  7. 7. Apply the update following standard change management procedures
  8. 8. Verify the upgrade was successful and test that the application functions normally

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Autosave Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-32949 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-32949 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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