PatchTheCVEautosave vulnerabilities and fixes
Recent CVEs affecting autosave, with upgrade or downgrade steps. 7 tracked.
autosave has 7 tracked vulnerabilities, 2 critical. A fixed release or vendor patch exists for 7. Most recent: 2022-04-01. Highest priority: CVE-2021-32933 (score 57/100).
- CVE-2021-32961 HIGH 7.5 UPGRADE UPGRADE A getfile function in MDT AutoSave versions prior to v6.02.06 enables a user to supply an optional parameter,
- CVE-2021-32957 HIGH 7.5 UPGRADE UPGRADE A function in MDT AutoSave versions prior to v6.02.06 is used to retrieve system information for a specific pr
- CVE-2021-32953 CRITICAL 9.8 UPGRADE UPGRADE An attacker could utilize SQL commands to create a new user MDT AutoSave versions prior to v6.02.06 and update
- CVE-2021-32949 HIGH 7.5 UPGRADE UPGRADE An attacker could utilize a function in MDT AutoSave versions prior to v6.02.06 that permits changing a design
- CVE-2021-32945 HIGH 7.5 UPGRADE UPGRADE An attacker could decipher the encryption and gain access to MDT AutoSave versions prior to v6.02.06.
- CVE-2021-32937 HIGH 7.5 UPGRADE UPGRADE An attacker can gain knowledge of a session temporary working folder where the getfile and putfile commands ar
- CVE-2021-32933 CRITICAL 10.0 UPGRADE UPGRADE An attacker could leverage an API to pass along a malicious file that could then manipulate the process creati
FAQ
How do I fix autosave vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is autosave being exploited right now?
None of the tracked autosave CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which autosave CVE should I patch first?
CVE-2021-32933 currently ranks highest (57/100): An attacker could leverage an API to pass along a malicious file that could then manipulate the process creati.